Here is your #MicrosoftCloudQuickFix – #MSIgnite has begun, and the Microsoft Ignite Cloud Skill Challenge is now open until November 9, 2022!
There are 7 challenges to choose from and once you complete a challenge you choose you earn a 𝗳𝗿𝗲𝗲 exam credit for a Microsoft Certification exam on your #MicrosoftLearning account!!!
Get ready to patch your on-premises versions of Exchange Server ASAP! This is today’s #MicrosoftCloudQuickFix !
Yet again as announced by #Microsoft on Friday September 30, 2022 there are two new reported zero-day vulnerabilities in Microsoft Exchange Server 2013, 2016, and 2019 that are being exploited…
CVE-2022-41040 is a Server-Side Request Forgery (SSRF) vulnerability and can only be exploited by authenticated attackers while CVE-2022-41082 allows remote code execution (RCE) when PowerShell is accessible to the attacker.
Microsoft has said it’s “working on an accelerated timeline” to provide a patch for the two newly disclosed vulnerabilities and while mitigations exist I would recommend a rapid patch deployment once one is available and of course always keeping your Exchange Servers up-to-date with the latest Cumulative Update (CU) and Security Updates (SU).
Microsoft indicated that #ExchangeOnline customers don’t need to take any action at the moment because the company has detections and mitigation in place and of course will apply the patch seamlessly once available – Anyone still need a business case for migration to #ExchangeOnline ?
For more information about this and Exchange Server Patching see:
In this episode Ryan McKay is joined by Andrew Lowes and discuss the deprecation of Basic Authentication in Microsoft 365 on October 1, 2022 and its impact to user experience along with the upcoming #MicrosoftIgnite2022
So you have done your due diligence and are sure your in the clear. You would like to manage this change and turn off Basic Authentication and test yourself before and not wait for Microsoft. That is todays #MicrosoftCloudQuickFix !
If you don’t have any Basic Authentication sign-ins then you can move on to block Basic Authentication for protocols on your tenant.
In your Microsoft 365 Admin Portal Next navigate to settings > Org Settings > under Services > Modern Authentication and ensure that “Turn on modern authentication for Outlook 2013 for Windows and later” is enabled and then under “Allow access to basic authentication protocols” uncheck any protocols you wish to no longer use Basic Authentication. Click “Save” and test.
There are three work weeks left until #Microsoft is scheduled to disable Basic Authentication access to Exchange Online. This is today’s #MicrosoftCloudQuickFix !
Back in September 2019 Microsoft announced they are disabling Basic Authentication access to Exchange Online to be replaced with Modern Authentication methods built on OAuth 2.0 token-based authorization. Modern Authentication has many improvements which mitigate issues with Basic Authentication and provide an improved security posture but as we are all aware there were circumstances in the world that pushed that date forward.
Beginning October 1, 2022 Microsoft will start disabling Basic Authentication for MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS), and Remote PowerShell access protocols on randomly selected Exchange Online tenants. You will know ahead of time when your tenant has been chosen by a posted message in your Microsoft365 Admin Center Messages 7 days beforehand and a post to the Service Health Dashboard notifications.
To prepare for this change check the Azure Active Directory Sign-In logs per New tools to block legacy authentication in your organization – Microsoft Tech Community which will help track down any clients still using Basic Authentication and allow you to update your clients as appropriate. After the change to your tenant any client using Basic Authentication for an affected protocol will be unable to connect and will receive an HTTP 401 error: bad username or password error.
If you don’t have any Basic Authentication sign-ins then there is nothing you need to do.
Microsoft does recognize you may not be ready to turn off Basic Authentication and there is a Self-Service Re-Enablement process outlined. Note: that this is a one time re-enablement of Basic Authentication which will last until the end of December 2022 only and during the first few weeks of 2023 any re-enabled protocols will be disabled again permanently.
In this episode Ryan McKay and Andrew Lowes discuss the retirement of the Classis Exchange Online Admin Center, advise where its features can be now be found in other spots in M365, and share fond memories of the Classic Exchange Online Admin Center!
Today’s #MicrosoftCloudQuickFix is that Exchange Server 2013 is reaching end of support in a little over 7 months from now. After April 11, 2023, #Microsoft will now longer provide technical support for problems that may occur, bug fixes for new issues that are discovered, security fixes for vulnerabilities that are discovered, and time zone updates.
In either case I highly recommend using the Exchange Deployment Assistant which is a web-based tool that asks you about your current Exchange environment and generates a custom step-by-step checklist that will help you.
Note: It is a supported coexistence scenario for Exchange 2019 and Exchange 2013 provided all your Exchange 2013 servers in your organization are patched to Exchange Server Cumulative Update 21 (CU21 – released June 2018) or higher. See Exchange Server build numbers and release dates
Microsoft has announced that Information Governance features currently available in the Classic Exchange Admin Center including Retention policies, Retention tags, and Journal rules are moving to the Microsoft Purview Compliance portal.
This is today’s #MicrosoftCloudQuickFix !
Retention Policies and Retention tags from messaging records management, and journaling rules are older compliance features that were originally managed in the Classic Exchange Admin Center. With the pending retirement of the Classic Exchange Admin Center forthcoming these features will not be brought forward to the new Exchange Admin Center but rather will be available as part of the Data Lifecycle Management solution found inside the Microsoft Purview Compliance portal under Data lifecycle management > Exchange (legacy).
Rollout of this change will begin in early August 2022 and is expected to be completed by the end of the month. Please advise your Exchange administrators or team responsible for Exchange compliance management and adjust access to the Microsoft Purview Compliance portal as needed.
Microsoft Cloud Quick Fix catches up with Andrew Lowes from @AzureTracks to discuss Microsoft Purview and all things compliance in the #MicrosoftCloud.