We’re updating the Company Branding component of the Azure Active Directory (Azure AD) sign-in page to enable customization capabilities for Self Service Password Reset (SSPR), footer hyperlinks and favicon.
This message is associated with Microsoft 365 Roadmap ID 88928.
We will begin retiring past versions of Azure Active Directory (Azure AD) Connect Sync 12 months from the date they are superseded by a newer version.
Key points
Today, as communicated on Tech Community, we are providing a reminder that the end of support for Azure Active Directory (Azure AD) Graph will be on June 30, 2022. Apps using Azure AD Graph after this time will no longer receive responses from the Azure AD Graph endpoint.
Since the Azure AD Graph APIs are being retired, we are also retiring the license assignment operation in the MSOnline and Azure AD PowerShell modules.
We are modifying the experience in the Microsoft Authenticator app when approving passwordless phone sign-in requests.
When will this happen:
The Azure Active Directory settings that control how users can create security and Microsoft 365 groups have been updated.
Note: If you do not have the Azure Active Directory (AAD) Premium P1 or the Azure Active Directory (AAD) Premium P2 license, you can safely ignore this message.
Ability to assign roles to Azure Active Directory groups is now generally available. Assigning roles to groups can simplify the management of role assignments in Azure Active Directory in two ways:
Note: If you have already transitioned to TLS 1.2, you can safely disregard this message.
As previously announced we will soon begin to retire support for following protocols and ciphers, in Azure Active Directory:
Many of our largest customers, typically in the banking and financial industries, are governed by strict standards. Their employees have access to very sensitive data and can only access that data within the boundaries of a single country. Admins currently restrict access to sensitive data based on IP address. However, IP address is less accurate and less reliable than GPS data. Thus, admins need the ability to restrict access based off of GPS data.
Now, admins will have the ability to create Conditional Access policies to allow/deny access using a new type of Named Location based off GPS data. When the policy is enabled, end users will need to share their GPS location from the mobile device on which Microsoft Authenticator is installed. The user’s mobile device is a good indication of the user’s actual location at the time.
We’ve created two new roles, Authentication policy administrator and Domain name administrator, to help reduce the number of Global Administrators in your organization.
This release of Code Match for Multi-Factor Authentication is available for Android and iOS and will allow you to turn on code matching for the Microsoft Authenticator app and apply the behavior to specific users or groups. Once enabled, users will be required to match the number on the sign-in screen with the number in the app.
This message is associated with Microsoft 365 Roadmap ID 70617.
I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.
Found my content useful?
Buy Me a Beer
HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
