Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

articles/active-directory/app-provisioning/media/use-scim-to-build-users-and-groups-endpoints/app-service-settings.png

@@ -11,14 +11,14 @@ items:
   - name: Tutorials
     expanded: true
     items:
-    - name: Plan provisioning for a SCIM endpoint 
-      href: use-scim-to-provision-users-and-groups.md
-    - name: Develop a sample SCIM endpoint
-      href: use-scim-to-build-users-and-groups-endpoints.md
-    - name: Customize attribute mappings
-      href: customize-application-attributes.md
     - name: App specific provisioning tutorials
       href: ../saas-apps/tutorial-list.md
+    - name: SCIM provisioning tutorials
+      items:
+      - name: Plan provisioning for a SCIM endpoint 
+        href: use-scim-to-provision-users-and-groups.md
+      - name: Develop a sample SCIM endpoint
+        href: use-scim-to-build-users-and-groups-endpoints.md
     - name: On-prem app provisioning tutorials
       items:
       - name: Provisioning to On-premises SCIM-enabled apps
@@ -27,6 +27,8 @@ items:
         href: on-premises-sql-connector-configure.md
       - name: Provisioning to LDAP based apps
         href: on-premises-ldap-connector-configure.md
+    - name: Customize attribute mappings
+      href: customize-application-attributes.md
   - name: Concepts
     expanded: true
     items: 

articles/active-directory/app-provisioning/media/use-scim-to-build-users-and-groups-endpoints/cloud-publish-2.png

@@ -8,16 +8,14 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 05/11/2021
+ms.date: 08/18/2022
 ms.author: kenwith
 ms.reviewer: arvinh
 ---
 
 # Tutorial: Develop a sample SCIM endpoint in Azure Active Directory
 
-No one wants to build a new endpoint from scratch, so we created some [reference code](https://aka.ms/scimreferencecode) for you to get started with [System for Cross-domain Identity Management (SCIM)](https://aka.ms/scimoverview). You can get your SCIM endpoint up and running with no code in just five minutes.
-
-This tutorial describes how to deploy the SCIM reference code in Azure and test it by using Postman or by integrating with the Azure Active Directory (Azure AD) SCIM client. This tutorial is intended for developers who want to get started with SCIM, or anyone interested in testing a SCIM endpoint.
+This tutorial describes how to deploy the SCIM [reference code](https://aka.ms/scimreferencecode) with  [Azure App Service](../../app-service/index.yml). Then, test the code by using Postman or by integrating with the Azure Active Directory (Azure AD) Provisioning Service. The tutorial is intended for developers who want to get started with SCIM, or anyone interested in testing a [SCIM endpoint](./use-scim-to-provision-users-and-groups.md). 
 
 In this tutorial, you learn how to:
 
@@ -28,11 +26,14 @@ In this tutorial, you learn how to:
 
 ## Deploy your SCIM endpoint in Azure
 
-The steps here deploy the SCIM endpoint to a service by using [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/) and [Azure App Service](../../app-service/index.yml). The SCIM reference code can also be run locally, hosted by an on-premises server, or deployed to another external service.
 
-1. Go to the [reference code](https://github.com/AzureAD/SCIMReferenceCode) from GitHub and select **Clone or download**.
+The steps here deploy the SCIM endpoint to a service by using [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/) and [Visual Studio Code](https://code.visualstudio.com/) with [Azure App Service](../../app-service/index.yml). The SCIM reference code can run locally, hosted by an on-premises server, or deployed to another external service.
+
+### Get and deploy the sample app
+
+Go to the [reference code](https://github.com/AzureAD/SCIMReferenceCode) from GitHub and select **Clone or download**. Select **Open in Desktop**, or copy the link, open Visual Studio, and select **Clone or check out code** to enter the copied link and make a local copy. Save the files into a folder where the total length of the path is 260 or fewer characters.
 
-1. Select **Open in Desktop**, or copy the link, open Visual Studio, and select **Clone or check out code** to enter the copied link and make a local copy.
+# [Visual Studio](#tab/visual-studio)
 
 1. In Visual Studio, make sure to sign in to the account that has access to your hosting resources.
 
@@ -55,11 +56,47 @@ The steps here deploy the SCIM endpoint to a service by using [Visual Studio 201
 
     ![Screenshot that shows publishing a new app service.](media/use-scim-to-build-users-and-groups-endpoints/cloud-publish-4.png)
 
-1. Go to the application in **Azure App Service** > **Configuration** and select **New application setting** to add the *Token__TokenIssuer* setting with the value `https://sts.windows.net/<tenant_id>/`. Replace `<tenant_id>` with your Azure AD tenant ID. If you want to test the SCIM endpoint by using [Postman](https://github.com/AzureAD/SCIMReferenceCode/wiki/Test-Your-SCIM-Endpoint), add an *ASPNETCORE_ENVIRONMENT* setting with the value `Development`.
 
-   ![Screenshot that shows the Application settings window.](media/use-scim-to-build-users-and-groups-endpoints/app-service-settings.png)
+# [Visual Studio Code](#tab/visual-studio-code)
+
+1. In Visual Studio Code, make sure to sign in to the account that has access to your hosting resources.
+
+1. In Visual Studio Code, open the folder that contains the *Microsoft.SCIM.sln* file.
+
+1. Open the Visual Studio Code integrated [terminal](https://code.visualstudio.com/docs/terminal/basics) and run the [dotnet restore](/nuget/consume-packages/install-use-packages-dotnet-cli#restore-packages) command. This command  restores the packages listed in the project files. 
+
+1. In the terminal, change the directory using the `cd Microsoft.SCIM.WebHostSample` command
+
+1. To run your app locally, in the terminal, run the .NET CLI command below. The [dotnet run](/dotnet/core/tools/dotnet-run) runs the Microsoft.SCIM.WebHostSample project using the [development environment](/aspnet/core/fundamentals/environments#set-environment-on-the-command-line).
+
+    ```dotnetcli
+    dotnet run --environment Development
+    ```
+
+1. If not installed, add [Azure App Service for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice) extension.
+
+1. To deploy the Microsoft.SCIM.WebHostSample app to Azure App Services, [create a new App Services](/azure/app-service/tutorial-dotnetcore-sqldb-app#2---create-the-app-service).
+
+1. In the Visual Studio Code terminal, run the .NET CLI command below. This command generates a deployable publish folder for the app in the bin/debug/publish directory.
+
+    ```dotnetcli
+    dotnet publish -c Debug
+    ```
+
+1. In the Visual Studio Code explorer, right-click on the generated **publish** folder, and select Deploy to Web App.
+1. A new workflow will open in the command palette at the top of the screen. Select the **Subscription** you would like to publish your app to.
+1. Select the **App Service** web app you created earlier.
+1. If Visual Studio Code prompts you to confirm, select **Deploy**. The deployment process may take a few moments. When the process completes, a notification should appear in the bottom right corner prompting you to browse to the deployed app.
+
+---
+
+### Configure the App Service
+
+Go to the application in **Azure App Service** > **Configuration** and select **New application setting** to add the *Token__TokenIssuer* setting with the value `https://sts.windows.net/<tenant_id>/`. Replace `<tenant_id>` with your Azure AD tenant ID. If you want to test the SCIM endpoint by using [Postman](https://github.com/AzureAD/SCIMReferenceCode/wiki/Test-Your-SCIM-Endpoint), add an *ASPNETCORE_ENVIRONMENT* setting with the value `Development`.
+
+![Screenshot that shows the Application settings window.](media/use-scim-to-build-users-and-groups-endpoints/app-service-settings.png)
 
-   When you test your endpoint with an enterprise application in the [Azure portal](use-scim-to-provision-users-and-groups.md#integrate-your-scim-endpoint-with-the-azure-ad-scim-client), you have two options. You can keep the environment in `Development` and provide the testing token from the `/scim/token` endpoint, or you can change the environment to `Production` and leave the token field empty.
+When you test your endpoint with an enterprise application in the [Azure portal](use-scim-to-provision-users-and-groups.md#integrate-your-scim-endpoint-with-the-azure-ad-provisioning-service), you have two options. You can keep the environment in `Development` and provide the testing token from the `/scim/token` endpoint, or you can change the environment to `Production` and leave the token field empty.
 
 That's it! Your SCIM endpoint is now published, and you can use the Azure App Service URL to test the SCIM endpoint.