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. The most prominent example of this is Microsoft Teams. What exactly happens when Exchange Online provisions a mailbox depends on different factors. Especially when using hybrid identities synchronized with Azure AD Connect, there are essential points to consider.
M365 - Exchange Online Center
ENow Software's Microsoft Exchange Online blog built by Microsoft MVPs for IT/Sys Admins.
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. Back in 2018, the Exchange product group announced that there would be no further development for the EWS protocol in Exchange Online. Indirectly, the EWS Managed API README-file on GitHub contains an announcement for Exchange Server.
Last week Microsoft announced that, effective October 1, 2022, they will begin to permanently disable Basic Auth in all tenants, regardless of usage (with the exception of SMTP Auth, which can still be re-enabled after that). Why the sudden change from their February 2021 announcement about postponing disabling Basic Auth for protocols in active use by tenant until further notice, but that they would continue to disable Basic Auth for all protocols not being used? We have the answers and the FAQs for you.
The Confusing Case of Cross-Forest Delegation
If you've even 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. Depending on who you ask, you'll get all kinds of different answers about what works when. In this blog post I will explain the confusing case of cross-forest delegation, and what you can expect to work or not work.
There is no cross-forest delegation
Much of the success of Office 365 is built on the Exchange hybrid migration. Since the initial release of Office 365 it has been possible to connect your on-premises Exchange organization to Exchange Online and have the two organization work almost like a single Exchange deployment. In the early days getting hybrid to work was a long and complicated process, but it was possible. The introduction of the hybrid configuration wizard has made the process of configuring hybrid Exchange much better.
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.
In Microsoft Exchange Server 2013, the Outlook Anywhere feature, formerly known as RPC over HTTP, lets clients who use Microsoft Outlook 2013, Outlook 2010, or Outlook 2007 connect to their Exchange servers from outside the corporate network or over the Internet using the RPC over HTTP Windows networking component. This topic describes the Outlook Anywhere feature and lists the benefits of using Outlook Anywhere.