Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into lb-basic-overview

Author: asudbring

articles/active-directory-b2c/find-help-open-support-ticket.md

@@ -75,10 +75,13 @@ If you're unable to find answers by using self-help resources, you can open an o
 
     1. Select a **[Severity](https://azure.microsoft.com/support/plans/response)**, and your preferred contact method.
 
+    > [!NOTE]
+    > Under **Advanced diagnostic information**, it's highly recommended that you allow the collection of advanced information by selecting **Yes**. It enables Microsoft support team to investigate the issue faster.
 
     :::image type="content" source="media/find-help-and-submit-support-ticket/find-help-and-submit-support-ticket-1.png" alt-text="Screenshot of how to find help and submit support ticket part 1.":::
 
     :::image type="content" source="media/find-help-and-submit-support-ticket/find-help-and-submit-support-ticket-2.png" alt-text="Screenshot of how to find help and submit support ticket part 2.":::
+
 
 1. Select **Next**. Under **4. Review + create**, you'll see a summary of your support ticket. 
 

articles/active-directory/app-provisioning/functions-for-customizing-application-data.md

@@ -7,7 +7,7 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.workload: identity
 ms.topic: reference
-ms.date: 02/16/2022
+ms.date: 04/13/2022
 ms.author: kenwith
 ms.reviewer: arvinh
 ---
@@ -1237,6 +1237,18 @@ Generate a user alias by taking first three letters of user's first name and fir
 * **INPUT** (surname): "Doe"
 * **OUTPUT**:  "JohDoe"
 
+### Add a comma between last name and first name. 
+Add a comma between last name and first name. 
+
+**Expression:** 
+`Join(", ", "", [surname], [givenName])`
+
+**Sample input/output:** 
+
+* **INPUT** (givenName): "John"
+* **INPUT** (surname): "Doe"
+* **OUTPUT**:  "Doe, John"
+
 
 ## Related Articles
 * [Automate User Provisioning/Deprovisioning to SaaS Apps](../app-provisioning/user-provisioning.md)

articles/active-directory/app-provisioning/on-premises-application-provisioning-architecture.md

@@ -13,7 +13,7 @@ ms.author: billmath
 ms.collection: M365-identity-device-management
 ---
 
-# Azure AD on-premises application provisioning architecture (preview)
+# Azure AD on-premises application identity provisioning architecture (preview)
 
 ## Overview
 
@@ -134,19 +134,19 @@ You can also check whether all the required ports are open.
      - Microsoft Azure AD Connect Agent Updater
      - Microsoft Azure AD Connect Provisioning Agent Package
 
-### Provisioning agent history
+## Provisioning agent history
 This article lists the versions and features of Azure Active Directory Connect Provisioning Agent that have been released. The Azure AD team regularly updates the Provisioning Agent with new features and functionality. Please ensure that you do not use the same agent for on-prem provisioning and Cloud Sync / HR-driven provisioning.
 
 Microsoft provides direct support for the latest agent version and one version before.
 
-## Download link
+### Download link
 You can download the latest version of the agent using [this link](https://aka.ms/onpremprovisioningagent).
 
-## 1.1.846.0
+### 1.1.846.0
 
 April 11th, 2022 - released for download
 
-### Fixed issues
+#### Fixed issues
 
 - We added support for ObjectGUID as an anchor for the generic LDAP connector when provisioning users into AD LDS. 
 

articles/app-service/includes/tutorial-dotnetcore-sqldb-app/visual-studio-code-deploy-app-service-02.md

@@ -5,10 +5,16 @@ ms.topic: include
 ms.date: 02/03/2022
 ---
 
-1. Select the Azure icon on the left navigation and expand the subscriptions to find the **coreSqlXYZ** App Service you created previously.
+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/release/publish` directory.
 
-1. Right-click on the **App Service** node and select **Deploy to Web App**.
+    ```dotnetcli
+    dotnet publish -c Release
+    ```
 
-1. A prompt will appear to select the folder to deploy.  If root of the project is already suggested, choose that option, otherwise select the **Browse** button to select the root folder from the file explorer.
+1. Right-click on the generated `publish` folder in the Visual Studio Code explorer and select **Deploy to Web App**.
 
-When the deployment completes, you should see a VS Code notification prompting you to browse to the deployed 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.
+
+If Visual Studio Code prompts you to confirm, click **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.

articles/app-service/media/tutorial-dotnetcore-sqldb-app/visual-studio-code-publish-folder-small.png

@@ -8,7 +8,7 @@ ms.assetid: 0a84734e-b5c1-4264-8d1f-77e781b28426
 ms.service: app-service
 ms.workload: web
 ms.topic: article
-ms.date: 08/04/2021
+ms.date: 04/08/2022
 ms.author: madsd
 ms.custom: seodec18, devx-track-azurecli 
 ms.devlang: azurecli
@@ -26,7 +26,7 @@ For more information and pricing. Go to the [NAT gateway overview](../../virtual
 :::image type="content" source="./media/nat-gateway-integration/nat-gateway-overview.png" alt-text="Diagram shows Internet traffic flowing to a NAT gateway in an Azure Virtual Network.":::
 
 > [!Note] 
-> * Using NAT gateway with App Service is dependent on virtual network integration, and therefore **Standard**, **Premium**, **PremiumV2** or **PremiumV3** App Service plan is required.
+> * Using NAT gateway with App Service is dependent on virtual network integration, and therefore a supported App Service plan pricing tier is required.
 > * When using NAT gateway together with App Service, all traffic to Azure Storage must be using private endpoint or service endpoint.
 > * NAT gateway cannot be used together with App Service Environment v1 or v2.
 

articles/app-service/media/tutorial-dotnetcore-sqldb-app/visual-studio-code-publish-folder.png

@@ -3,7 +3,7 @@ title: Integrate your app with an Azure virtual network
 description: Integrate your app in Azure App Service with Azure virtual networks.
 author: madsd
 ms.topic: conceptual
-ms.date: 03/04/2022
+ms.date: 04/08/2022
 ms.author: madsd
 
 ---
@@ -158,7 +158,7 @@ After your app integrates with your virtual network, it uses the same DNS server
 
 There are some limitations with using regional virtual network integration:
 
-* The feature is available from all App Service deployments in Premium v2 and Premium v3. It's also available in Standard but only from newer App Service deployments. If you're on an older deployment, you can only use the feature from a Premium v2 App Service plan. If you want to make sure you can use the feature in a Standard App Service plan, create your app in a Premium v3 App Service plan. Those plans are only supported on our newest deployments. You can scale down if you want after the plan is created.
+* The feature is available from all App Service deployments in Premium v2 and Premium v3. It's also available in Basic and Standard tier but only from newer App Service deployments. If you're on an older deployment, you can only use the feature from a Premium v2 App Service plan. If you want to make sure you can use the feature in a Standard App Service plan, create your app in a Premium v3 App Service plan. Those plans are only supported on our newest deployments. You can scale down if you want after the plan is created.
 * The feature can't be used by Isolated plan apps that are in an App Service Environment.
 * You can't reach resources across peering connections with classic virtual networks.
 * The feature requires an unused subnet that's an IPv4 `/28` block or larger in an Azure Resource Manager virtual network.
@@ -257,7 +257,7 @@ The regional virtual network integration feature has no extra charge for use bey
 
 Three charges are related to the use of the gateway-required virtual network integration feature:
 
-* **App Service plan pricing tier charges**: Your apps need to be in a Standard, Premium, Premium v2, or Premium v3 App Service plan. For more information on those costs, see [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/).
+* **App Service plan pricing tier charges**: Your apps need to be in a Basic, Standard, Premium, Premium v2, or Premium v3 App Service plan. For more information on those costs, see [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/).
 * **Data transfer costs**: There's a charge for data egress, even if the virtual network is in the same datacenter. Those charges are described in [Data transfer pricing details](https://azure.microsoft.com/pricing/details/data-transfers/).
 * **VPN gateway costs**: There's a cost to the virtual network gateway that's required for the point-to-site VPN. For more information, see [VPN gateway pricing](https://azure.microsoft.com/pricing/details/vpn-gateway/).