There were several tasks that needed to be completed to successfully migrate away from Microsoft 365. I decided that I would test different solutions and make changes as needed, but the move away from Microsoft 365 would be a one-way trip. I had no intention of going back to that platform, and I was going to make whatever solution I ended up with work for me. At the end of this migration, I was able to have a proper email and groupware solution that did everything I needed it to do, and it was on a non-US provider.

I have been stuck in a loop for a while using multiple services from different providers to get things done in my daily workflow. I have been looking for ways to consolidate and simplify those services as much as possible, as I am tired of dealing with multiple providers for everyday tasks. I have written about this several times on this website, and I have made a lot of efforts to reduce the number of services that I am using. Obviously, this is not a problem for a lot of people, and they have no issues switching back and forth between services, but I find it to be quite annoying and distracting. After going back and forth and tracking my usage, I decided that I no longer need Microsoft 365 at all, and it was time for it to go. The Microsoft 365 services that are offered can be provided elsewhere, and that was what I wanted to investigate.

This article from Windows Central came up the other day and it sums up a lot of the current issues with the consumer side of Microsoft, not necessarily on the Azure or Office 365 sides. Obviously, short term gains are most publicly traded companies primary concern, but Microsoft is no longer playing the long game on its core products and services, and it is starting to erode trust in the company. Overall, a good read and worth the time to go through it.

I ran into a somewhat annoying issue with using Mail Flow Rules with Exchange Online to modify the subject header on emails that were sent to aliases on some of my Office 365 accounts. I wanted to modify the email subject of those emails to show what alias it was meant for, and I figured I should share that process here if someone else runs into the same issue. This isn’t something that I do very often, and I was doing it wrong from the beginning, hence why I was having an issue.

I found a useful resource a few days ago that lists all the known/major Microsoft Administration Portals on a single website. While it is a great resource, it also represents a lot of the frustrations that I have with Microsoft’s online services and how administrators are expected to manage them.