‘Replace’ Policy Action in Safe Attachments Retiring – Microsoft Defender for Office 365

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

Azure AD Connect V1.x End of Support

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

Reminder – Exchange Server 2013 End of Support April 2023

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.

Upgrade to Exchange Server 2019 – See the following page on Microsoft Docs for Exchange Server system requirements and/or

Migrate to Exchange Online – See Decide on a migration path in Exchange Online on Microsoft Docs

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 #Microsoft365 #ExchangeOnline #MicrosoftExchange #MicrosoftCloudQuickFix

Data Lifecycle Management – Classic Exchange Admin Centre features migrating to Microsoft Purview Compliance portal

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.

For more information about data lifecycle management in Microsoft Purview Data Lifecycle Management see Learn about Microsoft Purview Data Lifecycle Management – Microsoft Purview (compliance) | Microsoft Docs

#Microsoft #Microsoft365 #MicrosoftPurview 
#MicrosoftCloudGovernance #MicrosoftCloudQuickFix

Upgrade to the latest version of Azure AD Connect before August 31, 2022

Today’s #MicrosoftCloudQuickFix is that Microsoft is retiring all V1.x versions of Azure Active Directory (Azure AD) Connect on August 31, 2022. To remain supported you must upgrade to the most recent version of Azure AD Connect V2!

Azure AD Connect was released several years ago. Since that time, several of the components that Azure AD Connect uses have been scheduled for deprecation and updated to newer versions. #Microsoft has bundled the newer components into a single release so you only have to update once. This release is Azure AD Connect V2.

If you continue with a retired version of Azure AD Connect after August 31, 2022 it might unexpectedly stop working, not have the latest security fixes, lack performance improvements and service enhancements, or if you require support #Microsoft you may be turned away!

Note: Azure AD Connect V2 requires Windows Server 2016 and above since it contains SQL Server 2019 components which are not supported on older versions of Windows Server.

Upgrading from V1.x is fully supported and for complete Azure AD Connect Upgrade V2 instructions see Azure AD Connect: Upgrade from a previous version – Microsoft Entra | Microsoft Docs

#Microsoft365 #AzureActiveDirectory #AzureADConnect #MicrosoftCloudQuickFix

Retirement of Exchange Online PowerShell with MFA

Microsoft is retiring the “Exchange Online PowerShell module with MFA” on December 31, 2022 with support for the module ending this month on August 31, 2022.

This is today’s #MicrosoftCloudQuickFix !

It is recommended to now use the Exchange Online PowerShell V2 module (EXO V2 module), which uses modern authentication and supports accounts with or without MFA.

If your like me you have a lot of updating to do to some old Exchange Online management scripts written with the older V1 module but, as an added bonus, there are a bunch of stunning exclusive Exchange Online PowerShell cmdlets that are optimized for bulk data retrieval scenario. Check out About the Exchange Online PowerShell V2 module for more information about these new cmdlets.

For installation and connection instructions, see Install and maintain the Exchange Online PowerShell V2 module andΒ Connect to Exchange Online PowerShell.

#MicrosoftCloudQuickFix #Microsoft365 #ExchangeOnline

Microsoft Book of News is out

#Microsoft Ignite may be over but all the announcements can be found in one place in the π— π—Άπ—°π—Ώπ—Όπ˜€π—Όπ—³π˜ π—œπ—΄π—»π—Άπ˜π—² 𝗕𝗼𝗼𝗸 𝗼𝗳 π—‘π—²π˜„π˜€ found here:

https://news.microsoft.com/ignite-november-2021-book-of-news/

Lots of news worthy announcements from new Azure VM’s, new Azure Arc-enabled features, on-demand disk bursting, to Context IQ, Microsoft Loop, Microsoft Mesh, and Microsoft Defender for Business!

Another #MSIgnite in the books but there is lots more exciting technology to use!

Thank-you #Microsoft for an awe-inspiring event!

Native External Sender Alerts on emails in Outlook

#Microsoft has released native External Sender Alerts on emails in Outlook for #ExchangeOnline email. This is today’s #MicrosoftCloudQuickFix !

It is hard to find that balance between user experience and cybersecurity and in today’s #HybridWorkplace it is as important as ever.

In the past to draw the attention of users to email which has come from external sources Exchange Administrators have leveraged Mail Flow rules (formerly Transport rules) to prepend to the subject line or insert to the message body to show the email is from external senders.

This approach has its limitations and can make reading the preview of email on mobile devices troublesome.

With Native External Sender Alerts on emails in Outlook for #ExchangeOnline email a new user experience is enabled. Note: Only Outlook products are supported on Windows, Mac, iOS, Android and Outlook on the web.

Outlook on the web, Mac, and mobile will display an External tag in the message list. Outlook Desktop and OWA will show the sender’s email address at reading pane info bar.

Outlook on the web view of External sender:

In Outlook for iOS:

The feature is enabled thru PowerShell and may take 24-48 hours to become active. Don’t forget to disabled the old Mail Flow rule!

Check out this Microsoft Docs page for more details on Set-ExternalInOutlook PowerShell cmdlet to enable External Sender Alerts on emails in Outlook in for Exchange Online email!

#MicrosoftCloudQuickFix #Microsoft365 #ExchangeOnline

Advanced Threat Protection (ATP) Safe Links in Teams

Today’s #MicrosoftCloudQuickFix is that #Microsoft has completed the rollout of Advanced Threat Protection Safe Links in #MicrosoftTeams to production and government #Microsoft365 tenants!

With this update, Microsoft brings the premium security of Window Defender for Office 365 Safe Links into #MicrosoftTeams clients!

ATP Safe Links for Teams checks that the links people click on in Teams are safe the moment that an end user clicks the link. If the link is flagged as malicious, ATP Safe Links will show a block page. All links throughout Teams including in chats, channels, and tabs are protected.

thumbnail image 1 captioned Figure 1: Safe Links prevents users from accessing malicious sites

To enable ATP Safe Links to protect users in Microsoft Teams, create or modify a Safe Links policy in the Microsoft 365 Defender Portal under Threat Policies then Safe Links.

Check out this Microsoft Docs page for more details on Safe Links in Microsoft Defender for Office 365!

#MicrosoftCloudQuickFix #Microsoft365 #MicrosoftDefender #MicrosoftTeams

PSTN Service Desk email support transition

Today’s exciting #MicrosoftCloudQuickFix is that beginning July 22, 2021 #Microsoft has transitioned to a new process to interact with the PSTN service desk for phone number porting and order support!

If you have been working to port numbers to #MicrosoftTeams in the past you will appreciate the ease of now being able to open tickets, view tickets, and track communication in the brand new Phone Number Service Center portal (of course hosted as a #PowerAppsPortal) that is integrated within the Teams Admin Center!

To access the new Phone Number Service Center portal open the #MicrosoftTeams Admin Center and then select “Voice” and then “Phone numbers”. At the top right click “Get phone number support”

From the Phone Number Service Center portal you can get help with porting numbers to Microsoft, or if you require help purchasing net new phone numbers from Microsoft.

Check out this Microsoft Docs page for more details on the new PTSN Service Desk!