Microsoft recently released a blogpost about deprecating Remote PowerShell in Exchange Online. It’s a small blog, but the impact can be serious. Exchange Online PowerShell is (was) available in three different versions and I will discuss these briefly.
M365 - Exchange Online Center
ENow Software's Microsoft Exchange Online blog built by Microsoft MVPs for IT/Sys Admins.
Exchange Online has different ways to provision mailboxes. Exchange Online is a standard service within Microsoft 365, which in the simplest case provides a mailbox. However, an Exchange Online mailbox also serves as a storage location for user-related data from other Microsoft 365 services.
When users report to IT support that Exchange Online delivers email messages to the Junk Email folder of their mailbox incorrectly, the reason is often a misconfiguration of Exchange Online Protection settings. Such a situation mainly affects Exchange Hybrid configurations that use the centralized message flow.
Exchange Web Services (EWS) have been an integral part of Exchange since Exchange Server 2007. They are used not only by Exchange Server and Exchange Online for communication between Exchange Servers and as part of hybrid communication. Email clients also use web services. EWS is a SOAP-based API, but in the meantime, there are more modern protocols.
Last week Microsoft announced that, effective October 1, 2022, they will beginto permanently disable Basic Auth in all tenants, regardless of usage (with the exception of SMTP Auth). Why the sudden change from their February 2021 announcement about postponing disabling Basic Auth for protocols in active use by tenant until further notice, yet Microsoft would continue to disable Basic Auth for all protocols not being used? We have the answers and the FAQs for you.
If you've ever participated in an Exchange Online migration at almost any level, it's likely you've run into the issue of cross-forest delegation. You know that Exchange allows you to delegate rights from one mailbox to another, allowing users to access other mailboxes. When you do an Exchange hybrid migration, there are some special considerations you have to take to keep these delegated rights working.
Almost every enterprise today is going through some type of transformation from historic compute solutions (i.e., “running IT in our data center”) to hybrid environments where workloads are distributed to specific locations, platforms, or providers based on business requirements. Even organizations seeking to be “cloud only” or “completely hyperconverged” will still have many environment types within their landscape. “IT everywhere” includes all the places we’d like to shift away from, like traditional corporate data centers, but won’t be able to due to technical debt and legacy systems.
I expect we all know there are limits to what you can and cannot do with your Exchange Online mailbox. We all know there is a limit to how many emails you can send and receive, how much storage you can use, how much data you can move into or out of Exchange Online, and how big each individual email can be. However, I find that few Exchange Online administrators know exactly what those limits are, how they work, why they are there, or what you can do about them.
Now that the long frigid months of winter have passed, spring is the time to open the windows, sweep away the cobwebs, and start anew. While most IT leaders would agree that keeping the IT house in order is very much a year-round effort, spring brings a reminder to pull out the white gloves and take a closer look for any technical debt hiding in the dusty corners. And your first order of business should be to begin re-assessing your Microsoft Exchange and Office 365 management strategy.