Workplace update

Author: ArvindHarinder1

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

@@ -18,12 +18,33 @@ ms.author: jeedes
 
 ms.collection: M365-identity-device-management
 ---
+
 # Tutorial: Configure Workplace by Facebook for automatic user provisioning
 
 This tutorial describes the steps you need to perform in both Workplace by Facebook and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Workplace by Facebook](https://work.workplace.com/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../manage-apps/user-provisioning.md).
 
-> [!NOTE]
-> The Azure AD third party application in Workplace by Facebook has been approved. Customers will not have an interruption of service on December 16th. You will see a note in the Workplace by Facebook Admin console indicating a deadline of 28-February-2020 by when you will need to transition to the new application. We are working to keep the transition as simple as possible and will provide an update here on the transition by end of month.
+## Migrating to the new Workplace by Facebook application
+#### What's changing?
+* 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 the Workplace. 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 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 to your URL to save credentials again. 
+
+https://portal.azure.com/**?Microsoft_AAD_IAM_userProvisioningEnableCredentialsOverride=true**
+
+ 
+#### 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. 
+
+ 
+#### 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 in February. The migration will be completed for all tenants by the end of the Month. 
 
 ## Capabilities supported
 > [!div class="checklist"]
@@ -163,4 +184,4 @@ Once you've configured provisioning, use the following resources to monitor your
 
 ## Next steps
 
-* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md)
+* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md)