Update reference-breaking-changes.md

Author: hpsin

articles/active-directory/develop/reference-breaking-changes.md

@@ -37,19 +37,19 @@ None scheduled at this time.  Please see below for the changes that are in or ar
 
 ### Azure Government endpoints are changing
 
-**Effective date**: May 5th (Finishing June 8th) 
+**Effective date**: May 5th (Finishing June 2020) 
 
 **Endpoints impacted**: All
 
 **Protocol impacted**: All flows
 
-On 1 June 2018, the official Azure Active Directory (AAD) Authority for Azure Government changed from `https://login-us.microsoftonline.com` to `https://login.microsoftonline.us`. This change also applied to Microsoft 365 GCC High and DoD, which Azure Government AAD also services.
-
-If you own an application within a US Government tenant, you must update your application to sign users in on the `.us` endpoint.  For more details, app developers should search their inboxes for an email with the subject "Action required: Update Azure AD Authenticated Apps and Cloud Management Tools by 5 May 2020" - this email will contain a list of the applications that will be impacted by this change. 
+On 1 June 2018, the official Azure Active Directory (AAD) Authority for Azure Government changed from `https://login-us.microsoftonline.com` to `https://login.microsoftonline.us`. This change also applied to Microsoft 365 GCC High and DoD, which Azure Government AAD also services. If you own an application within a US Government tenant, you must update your application to sign users in on the `.us` endpoint.  
 
 Starting May 5th, Azure AD will begin enforcing the endpoint change, blocking government users from signing into apps hosted in US Government tenants using the public endpoint (`microsoftonline.com`).  Impacted apps will begin seeing an error `AADSTS900439` - `USGClientNotSupportedOnPublicEndpoint`. This error indicates that the app is attempting to sign in a US Government user on the public cloud endpoint. If your app is in a public cloud tenant and intended to support US Government users, you will need to [update your app to support them explicitly](https://docs.microsoft.com/azure/active-directory/develop/authentication-national-cloud). This may require creating a new app registration in the US Government cloud. 
 
-Enforcement of this change will be done using a gradual rollout - a temporary 4 hour enforcement for a limited tier of apps, then an 8 hour enforcement, then a permanent enforcement.  This will be done in three tiers based on how frequently users from the US Government cloud sign in to those apps - less than once per 10 minutes, less than once per minute, and finally apps signing in US Government users more than once per minute.  These outages and enforcements will take place on Mondays and Wednesdays. By mid-June Azure AD will have this fully enforced across all applications. 
+Enforcement of this change will be done using a gradual rollout based on how frequently users from the US Government cloud sign in to the application - apps signing in US Government users infrequently will see enforcement first, and apps frequently used by US Government users will be last to have enforcement applied. We expect enforcement to be complete across all apps in June 2020. 
+
+For more details, please see the [Azure Government blog post on this migration](https://devblogs.microsoft.com/azuregov/azure-government-aad-authority-endpoint-update/). 
 
 ## March 2020