Merge pull request #188083 from jcruiz/patch-3

Android Authenticator update

Author: PRMerger3

articles/active-directory/verifiable-credentials/whats-new.md

@@ -20,10 +20,11 @@ This article lists the latest features, improvements, and changes in the Azure A
 
 ## February 2022
 
-We are rolling out some important updates to our service that are breaking changes and require Azure AD Verifiable Credentials service reconfiguration.
+We are rolling out some important updates to our service that are breaking changes and require Azure AD Verifiable Credentials service reconfiguration and re-issuance of verifiable credentials for end-users.
 
 - The Azure AD Verifiable Credentials service can now store and handle data processing in the Azure European region. [More information](whats-new.md?#azure-ad-verifiable-credentials-available-in-europe)
-- Azure AD Verifiable Credentials customers can take advantage of enhancements to credential revocation that add a higher degree of privacy through the implementation of the [W3C Status List 2021](https://w3c-ccg.github.io/vc-status-list-2021/) standard. [Read more](whats-new.md?#credential-revocation-with-enhanced-privacy)
+- Azure AD Verifiable Credentials customers can take advantage of enhancements to credential revocation that add a higher degree of privacy through the implementation of the [W3C Status List 2021](https://w3c-ccg.github.io/vc-status-list-2021/) standard. [More information](whats-new.md?#credential-revocation-with-enhanced-privacy)
+- We made protocol updates in Microsoft Authenticator in the interaction between the Issuer of a verifiable credential and the user preenting the verifiable credential. This update will force all Verifiable Crecentials to be re-issued in Microsoft Authenticator for Android. [More information](whats-new.md?#microsoft-authenticator-android-did-generation-update)
 
 >[!IMPORTANT]
 > All Azure AD Verifiable Credential customers receiving a banner notice in the Azure portal need to go through a service reconfiguration before March 31st 2022. On March 31st 2022 tenants that have not been reconfigured will lose access to any previous configuration. Administrators will have to set up a new instance of the Azure AD Verifiable Credential service. Learn more about how to [reconfigure your tenant](verifiable-credentials-faq.md?#how-do-i-reconfigure-the-azure-ad-verifiable-credentials-service).
@@ -96,6 +97,10 @@ Sample contract file:
 >[!IMPORTANT]
 > You have to reconfigure your Azure AD Verifiable Credential service instance to create your new Identity hub endpoint. You have until March 31st 2022, to schedule and manage the reconfiguration of your deployment. On March 31st, 2022 deployments that have not been reconfigured will lose access to any previous Azure AD Verifiable Credentials service configuration. Administrators will need to set up a new service instance.
 
+### Microsoft Authenticator Android DID Generation Update
+
+We are making protocol updates in Microsoft Authenticator to support Single Long Form DID, thus deprecating the use of pairwise. With this update your DID in Microsoft Authenticator will be used of every issuer and relaying party exchange. Holders of verifiable crendentials in Microsoft Authenticator for Android must get their verifiable credentials re-issued as any previous credentials are not going to continue working. 
+
 ## December 2021
 
 - We added [Postman collections](https://github.com/Azure-Samples/active-directory-verifiable-credentials/tree/main/Postman) to our samples as a quick start to start using the Request Service REST API.