Merge pull request #113067 from ArvindHarinder1/patch-110

Update workplacebyfacebook-provisioning-tutorial.md

Author: PRMerger9

articles/active-directory/saas-apps/workplacebyfacebook-provisioning-tutorial.md

@@ -13,7 +13,7 @@ ms.workload: identity
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 12/10/2019
+ms.date: 04/28/2020
 ms.author: jeedes
 
 ms.collection: M365-identity-device-management
@@ -30,25 +30,16 @@ If you have an existing integration with Workplace by Facebook, please see the b
 * Changes on the Azure AD side: The authorization method to provision users in Workplace has historically been a long lived secret token. Soon you will see the authorization method changed to the OAuth authorization grant. 
 * Changes on the Workplace side: Previously the Azure AD app was a custom integration in Workplace by Facebook. Now you will see Azure AD in the Workplace integrations directory as a third party application. 
 
- 
-
 #### What do I need to do to migrate my existing custom integration to the new application?
-If you have an existing Workplace integration with a valid token, **no action is required**. We are automatically migrating customers each week to the new application. This is done completely behind the scenes. If you can't wait and want to move to the new application manually, you can add a new instance of Workplace from the gallery, and configure provisioning again. All new instances of Workplace will automatically be using the new application version. 
-
+If you have an existing Workplace integration with a valid token, no action is required. **As of 04/28/2020 we have automatically migrated all applications that are not in quarantine due to invalid credentials.**
 
-If your Workplace integration is in quarantine, you will need to supply a valid token again in order for us to migrate you. The admin credentials section will be greyed out, but you can append the following (**?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true**) to your URL to save credentials again. 
-
-https://portal.azure.com/?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true
-
 #### How can I tell if my application has been migrated? 
-When your application is migrated, the banner in the authorization section about upcomming changes will be removed and the secret token field will be replaced with a blue authorize button. 
+* In the Azure Portal: When your application is migrated, the banner in the authorization section about upcoming changes will be removed and the secret token field will be replaced with a blue authorize button. 
+* In the Workplace by Facebook portal: Review the Azure AD app to ensure that it is approved.  
 
 #### The admin credentials section is greyed out on my application and I can't save. Why?
-We have locked down the admin credentials section for existing Workplace customers. When your tenant has been migrated to the new Workplace application you will be able to update the admin credentials section again. If you can't wait, you can use the URL above to edit your application. 
+We have locked down the admin credentials section for Workplace customers that have not migrated. Please use the following URL if the admin credentials section is greyed out and you need to authorize access again. **?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true** (https://portal.azure.com/?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true)
 
- 
-#### When will these changes happen?
-All new instances of Workplace will already be using the new integration / authorization method. Existing integrations will be migrated gradually by May. The workplace team has provided an extension on the deadline from Feb-28 to May-1. 
 
 ## Capabilities supported
 > [!div class="checklist"]