One situation I see often with customers is the desire to control and monitor file downloads from the cloud. For most organizations in most industries, it’s important to control your organization's data, and that data is often contained in files. The proprietary nature of information in files makes them very valuable to many organizations, and thusly important to control.
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.
Many organizations regard their people as their greatest asset. There is no disputing that the ability to hire great talent is a critical component to success, but in today’s pandemic-work-from-home world these great assets could also pose the greatest risk to your business. No amount of technology can account for human nature. You may already have invested in the best security solutions, but all it takes is a single click of a phishing email. I like to refer to this as a people problem – something that technology cannot solve entirely.
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.
While many of us are still holding onto summer, it is mid-September and Fall is just around the corner. And that means a fairly important Microsoft deadline will soon be upon us. As of November 1, 2021 only Outlook 2013 Service Pack 1 (with latest fixes) and later versions will be able to connect to Microsoft 365 services.
If you are experiencing problems with an Office 365 service, the native option is to check Microsoft’s Service Health Dashboard (SHD) in your Microsoft 365 Admin Center to determine whether this is a known issue with a resolution in progress before you call support or spend valuable time troubleshooting. However, the information that is provided through the SHD is only of limited use, as it focuses primarily on the overall service health instead of tenant-specific or user-specific problems.
Two organizations each have Microsoft 365 tenants and they want to work together on several projects – some of which run for a limited time and some of which are ongoing. How can these organizations enable their people and teams to collaborate more effectively and productively across their different tenants? Add on top of this, how can this be done in a secure and compliant manner? This article describes several key collaboration options that administrators at each organization can consider as shared goals.
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.