Your quick fix of all things Microsoft Cloud
Today I chat with Andrew Lowes about the new Exchange Online PowerShell V3 module.
#Microsoft #Microsoft365 #ExchangeOnline #MicrosoftCloudQuickFix
URLs shown in today’s video podcast include:
https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps
https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.0.0
Microsoft has released Exchange Online PowerShell V3 module. This is today’s #MicrosoftCloudQuickFix !
It is recommended to now use the Exchange Online PowerShell V3 module. Exchange Online cmdlets backed by the REST API are available in Exchange Online PowerShell V3. REST API cmdlets have the following advantages:
For installation and connection instructions, see Exchange Online Management 3.0.0 and Connect to Exchange Online PowerShell.
#MicrosoftCloudQuickFix #Microsoft365 #ExchangeOnline
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 !
As outlined in my previous blogpost to prepare for the 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.
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.
For more information check out the following Disable Basic authentication in Exchange Online | Microsoft Docs in Microsoft Docs.
#Microsoft365 #ExchangeOnline #BasicAuthentication #ModernAuthentication #MicrosoftCloudSecurity #MicrosoftCloudQuickFix
If you’re like me you enjoy the rich set of features included in Microsoft Defender for Office 365 including the Safe Links and Safe Attachments capabilities. Microsoft has announced a change to retire the ‘replace’ action in Safe Attachment policies and that is today’s #MicrosoftCloudQuickFix !
Safe Attachments in Microsoft Defender for Office 365 provides an additional layer of protection for email attachments that have already been scanned by anti-malware protection in Exchange Online Protection (EOP). Specifically, Safe Attachments uses a virtual environment to check attachments in email messages before they’re delivered thru a process know as detonation.
Safe Attachments protection is controlled by Safe Attachment policies configured in the Microsoft 365 Defender portal. In Safe Attachment policies one of the actions which can be applied to a message is the ‘Replace’ action which delivers only the message body to the recipient without the original attachments when it has been found to contain malware.
Beginning in September 2022 the ‘Replace’ action will be retired and no longer available for use in Safe Attachment policies. The first phase of the retirement will automatically apply the ‘Block’ action, which will quarantine the email, to any existing policies with the ‘Replace’ action specified.
The second phase of the retirement targeted to complete by late-October 2022 will remove the ‘Replace’ action altogether from the Microsoft Defender portal and any existing policies with it will be changed to use the ‘Block’ action.
There will not be a similar action to ‘Replace’ post retirement and we recommend that you review and update all applicable Safe Attachments policies in your tenant beforehand.
For more information on Safe Attachment policy settings in Microsoft Defender for Office 365 please see Safe Attachments – Office 365 | Microsoft Docs
#Microsoft #Microsoft365 #MicrosoftDefenderforOffice365 #MicrosoftCloudSecurity #MicrosoftCloudQuickFix
For the last few weeks we have been advising that all Azure Active Directory Connect V1.x versions would reach end of support on August 31, 2022. Well that’s tomorrow and in case you haven’t yet upgraded here is your #MicrosoftCloudQuickFix !
Azure Active Directory Connect supports a couple different methods for upgrading from previous versions from an in-place upgrade to a swing migration upgrade depending on the complexity of your deployment and/or if you need to upgrade Azure Active Directory Connect onto a newer version of the Windows Server Operating system. Windows Server 2016 is the minimum supported version of Windows Server but we recommended Windows Server 2022.
For both the in-place upgrade and swing methods please see the instructions contained in Azure AD Connect: Upgrade from a previous version to the latest. Specific to the swing method please see instructions on how to Import and export Azure AD Connect configuration settings.
Note: A handy tool is available from Microsoft to document and report on the current configuration of an Azure Active Directory Connect installation named Azure AD Connect Configuration Documenter. This tool can be used to create a comparison report for a swing migration.
#Microsoft365 #AzureActiveDirectory #AzureADConnect #MicrosoftCloudQuickFix
Microsoft Cloud Quick Fix catches up with Andrew Lowes from @AzureTracks to discuss Microsoft Purview and all things compliance in the #MicrosoftCloud.
URLs shown in today’s video podcast include:
Introduction to Microsoft Purview governance solutions – Microsoft Purview | Microsoft Docs
#Microsoft #Microsoft365 #MicrosoftPurview #MicrosoftCloudGovernance #MicrosoftCloudQuickFix
New to #Microsoft365 or performing some firewall/IPS changes or updates? Your #MicrosoftCloudQuickFix is this landing page which you can share with your network team to ensure your users have the best experience!
https://docs.microsoft.com/en-us/microsoftteams/office-365-urls-ip-address-ranges