How To Associate Your Microsoft Account With An Office 365 Exchange Hosted Email Address

Office 365 Exchange Online Plan 1 is great for hosting email on your personal domain. At £36 a year, aka £3 per month you get an enterprise grade Exchange inbox.

However if you have setup your domain in the Microsoft 365 admin center, then try to change the primary email address on your Microsoft Account to an email address hosted with Office 365 Exchange, you are greeted with the following error: “You can’t add a work or school email address as an alias to a personal Microsoft account. Please try another.”

So basically if your paying Microsoft to host email for your personal domain, you then can’t associate your Microsoft account with any email address on that domain, or can you?

Historically you could, however that changed in 2016 as this was apparently causing a great deal of confusion in some business between what an Office 365 account and Microsoft account was, so Microsoft blocked the ability to associate both with the same email address.

However I know things work fine if you do have both a Microsoft account and an Office 365 account associated with the same domain as i’ve been doing it for years with my personal eu domain. However due to the UK leaving the EU i’ve had to switch over to a domain, which is where i first discovered this issue.

However after a bit of messing about I did discover a way to associate both a personal Microsoft account and an Office 365 account with the same domain where email is hosted with Office 365 exchange.

First if you have associated your domain with Office 365 you need to delete your domain in

Delete Office 365 Domain

When you have deleted the domain you then need to wait a few hours for this to propagate to all Microsoft servers.

During this time you need to host email for the domain you wish to use in Office 365 elsewhere, if you have a webhosting account with gives you a few email inboxes this would be ideal.

If you have your domain registered with Namecheap, as long as your using Namecheap to host your domains DNS then you can add a catch all email address  for your domain in their admin panel, I simply did this to forward any incoming email’s to another inbox, such as a Gmail / Hotmail address:

Namecheap Catch All Email Forwarding

My domains DNS were hosted with Cloudflare, so I did have to temporary move them back to Namecheap to do this.

Once your domain has deleted from Office 365 and you can receive email with the domain you wish to use with your personal Microsoft Account and Office 365 elsewhere you can now log in to and click edit profile:

Edit Microsoft Account

On the edit profile page click “Manage how you sign in to Microsoft”, you should then be able to click “add email address” and do so without getting the error “You can’t add a work or school email address as an alias to a personal Microsoft account. Please try another.”

Microsoft Account Alias Office 365 Exchange Domain

If you do get the “You can’t add a work or school email address as an alias to a personal Microsoft account. Please try another.” then you need to wait a bit longer as it hasn’t propagated to all Microsoft’s servers that your domain is no longer hosted with Office 365.

You should now be able to add your desired email address to the Microsoft account you wish to also use Office 365 Exchange Email with and receive the confirmation email thanks to the email forwarding we setup above.

Once you have received the confirmation email you can set your new email address as your primary alias.

Now everything is set for the Microsoft account you can add your domain back to Office 365 and change your DNS settings to allow Office 365 Exchange to host your email, still having your Microsoft Account associated with the domain you are hosing email for on Office 365.

Hopefully this helps someone out who wishes to use Office 365 Exchange to host email for their personal domain. I can totally understand why Microsoft have blocked you from having both a Microsoft account and an Office 365 account hosted with the same domain, as it can get confusing if you don’t understand the difference between the two. However someone like me who just wants to use Office 365 Exchange to host their personal email I see no issue with this, everything has worked fine for me when Microsoft actually allowed this to be done.

What this does show is Microsoft really need to allow some official way for Office 365 / Microsoft accounts to be linked without causing confusion.

EU Domains To Be Revoked From UK Citizens, Faith In .EU Domains Lost

Years ago when looking at choosing a domain for my personal email and blog, I looked at various different domain options. In the end I settled on as it was available. Another perceived benefit was .eu was shorter to type than .com or (not that my name was available for either TDL’s).

I had little desire to purchase a vanity domain such as .blog for example, many of these are controlled by companies, which might not exist in the future, or significantly increase their prices at a later date. As you might have noticed many of these vanity domains get very expensive after the first year.

Anyway, after reading the Eurid website and concluding a .EU domain was for me I registered my domain, gradually transferring all my online accounts over to my .EU domain. Since then over the years I’ve also built this blog up, publishing articles when I have something worthwhile to share with like minded people.

Now fast forward to the present day, just over half the people in the UK who voted chose to leave the .EU. Unfortunately because  the UK is leaving the EU it appears UK citizens will have their .EU domains revoked. This is due to happen on the 31st March 2019 in a no-deal Brexit scenario, or on the 1st January 2021 with a deal in place according to Eurids Brexit notice.

Needless to say this poses a massive security risk to any UK citizen who purchased an .EU domain and is actively using it for their personal email / online presence. I now have to log in to every online service I use and change the email associated with that service to an alternative non .EU domain before 1st March 2019. After that I presume my domain will become available for registration again, if not immediately then at some point in the future.

This will allow anyone who purchases the domain in the future to recover any accounts I leave associated with my domain. In addition it will allow them to receive any email’s sent to me by contacts who don’t update their address book with my new email address.

Another major problem is I will also have to change this blogs domain from to a new non .EU domain, this means I will loose any linkbacks from other sites which link to my past blog posts. I can obviously redirect them in the time I still have control of, however once the domain is revoked those linkbacks are essentially useless.

Needless to say the EU are well and truly screwing over UK citizens who own .EU domains… if we have to have our domains revoked, it would be nice to have some assurances no one else will be allowed to register the domain anytime soon. As it stands at the moment a spammer / scammer could well own my domain this time next year.

With the above in mind I have to wonder what European citizen or business would knowingly purchase and use a .EU domain to use for anything worthwhile, knowing it could be revoked for political reasons out their control in the future. I suspect many never believed the UK would actually leave the EU, I certainly didn’t.

After Brexit it’s more than possible other counties could leave the EU in the future.

Hopefully European citizens think twice before purchasing an .EU domain, I certainly would if I was still going to be a citizen in an EU country. I’d recommend people stick to a domain extension which belongs to their country or the traditional .com, .net or .org domains.

.EU domains shouldn’t be seen as a safe option for any sort of web presence, I’ve certainly learned a hard lesson here.

CloudFlare Flexible SSL Redirect Loop Fix For WordPress / IIS

So you are hosting a WordPress Blog running on IIS (Internet Information Services) which is behind CloudFlare CDN (Content Distribution Network) and you want to enable CloudFlare’s free Flexible SSL so your WordPress Blog can be accessed over https. You have tried to set this up, however have ended up with an annoying a redirect loop leaving your WordPress Blog inaccessible, here is how to fix that redirect loop.

CloudFlare Flexible SSL Setup for WordPress Running On IIS:

  1. Log in to CloudFlare and find your domain
  2. Click the settings cog next to it and select “Cloudflare Settings”
  3. Scroll down to SSL and enable Flexible SSL


Next in your WordPress Admin Panel:

  1. Go to Settings
  2. Change your blogs URL’s from http:// to https://


You will have now forced WordPress to use https:// however you will find you now have the infamous redirect loop error.

Fix WordPress / CloudFlare Flexible SSL Redirect Loops:

  1. Open your wp-settings.php file and find the line which says require_once(ABSPATH . ‘wp-settings.php’)
  2. Before this line add the following code:
// Force Admin Login To SSL
define('FORCE_SSL_ADMIN', true); 
// CloudFlare SSL Fix
else {
$_SERVER['HTTPS'] = false;
define('WP_SITE_URI', ($_SERVER["HTTPS"]?"https://":"http://").$_SERVER["HTTP_HOST"]);
define('WP_SITEURI', ($_SERVER["HTTPS"]?"https://":"http://").$_SERVER["HTTP_HOST"]);
define("WP_CONTENT_URL", WP_SITE_URI . "/wp-content");                   
define("WP_CONTENT_URL", WP_SITE_URI . "/wp-content");

Add these after the require_once(ABSPATH . ‘wp-settings.php’) line:

wp_cache_set("siteurl_secure", "https://" . $_SERVER["SERVER_NAME"], "options");
wp_cache_set("home", WP_SITE_URI, "options");
wp_cache_set("siteurl", WP_SITE_URI, "options");

That should fix your WordPress / Cloudflare redirect loop problems when accessing your WordPress blog from behind Cloudflare, now you simply need to force all connections to your blog to use https, to do this:

  1. Log in to CloudFlare and find your domain
  2. Click the settings cog next to it and select “Page Rules”
  3. Select always use https
  4. enter ** for the rule patterns, in this example i entered **
  5. Click add rule


All your old http:// url’s will now 301 redirect to the https:// URL’s.

The 301 redirect tells Google and other search engines that the page has moved permanently.

Note: if you do not wish to force https on sub domains enter* for the page rule on Cloudflare instead.

That’s it, your WordPress Blog should now be working fine with CloudFlare Flexible SSL.

You can test your SSL setup with Qualys SSL Test, got a grade “A” test result, which is the highest you can obtain.