Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into self-service-working

Author: bjspeaks

articles/active-directory/saas-apps/github-enterprise-managed-user-tutorial.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 03/15/2021
+ms.date: 09/27/2022
 ms.author: jeedes
 
 ---
@@ -122,9 +122,9 @@ In this section, you'll take the information provided from AAD above and enter t
 1. Click on Sign In at the top-right corner
 1. Enter the credentials for the first administrator user account. The login handle should be in the format: `<your enterprise short code>_admin`
 1. Navigate to `https://github.com/enterprises/` `<your enterprise name>`. This information should be provided by your Solutions Engineering contact.
-1. On the navigation menu on the left, select **Settings**, then **Security**.
-1. Click on the checkbox **Enable SAML authentication**
-1. Enter the Sign on URL. This URL is the Login URL that you copied from AAD above.
+1. On the navigation menu on the left, select **Settings**, then **Authentication security**.
+1. Click on the checkbox **Require SAML authentication**
+1. Enter the Sign-on URL. This URL is the Login URL that you copied from AAD above.
 1. Enter the Issuer. This URL is the Azure AD Identifier that you copied from AAD above.
 1. Enter the Public Certificate. Please open the base64 certificate that you downloaded above and paste the text contents of that file into this dialog.
 1. Click on **Test SAML configuration**. This will open up a dialog for you to log in with your Azure AD credentials to validate that SAML SSO is configured correctly. Log in with your AAD credentials. you will receive a message **Passed: Successfully authenticated your SAML SSO identity** upon successful validation.

articles/active-directory/saas-apps/sciforma-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 06/16/2021
+ms.date: 09/26/2022
 ms.author: jeedes
 ---
 # Tutorial: Azure Active Directory integration with Sciforma
@@ -73,9 +73,12 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 4. On the **Basic SAML Configuration** section, perform the following steps:
 
     a. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
-    `https://<SUBDOMAIN>.sciforma.net/sciforma/saml`
+    `https://<SUBDOMAIN>.sciforma.net/sciforma`
 
-    b. In the **Sign on URL** text box, type a URL using the following pattern:
+    b. In the **Reply URL** text box, type a URL using the following pattern:
+    `https://<SUBDOMAIN>.sciforma.net/sciforma/saml/post`
+
+    c. In the **Sign on URL** text box, type a URL using the following pattern:
     `https://<SUBDOMAIN>.sciforma.net/sciforma/main.html`
 
 	> [!NOTE]

articles/active-directory/saas-apps/workhub-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 08/22/2022
+ms.date: 09/27/2022
 ms.author: jeedes
 
 ---
@@ -51,7 +51,7 @@ To configure the integration of workhub into Azure AD, you need to add workhub f
 1. In the **Add from the gallery** section, type **workhub** in the search box.
 1. Select **workhub** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
 
- Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, as well as walk through the SSO configuration as well. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides)
+ Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, and walk through the SSO configuration as well. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides)
 
 ## Configure and test Azure AD SSO for workhub
 
@@ -121,11 +121,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 ## Configure workhub SSO
 
-To configure single sign-on on **workhub** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [workhub support team](mailto:team_bkp@bitkey.jp). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **workhub** side, you need to send the downloaded **Certificate (Base64)**, and appropriate copied URLs from Azure portal to [workhub support team](mailto:support_work@bitkey.jp). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create workhub test user
 
-In this section, you create a user called Britta Simon at workhub. Work with [workhub support team](mailto:team_bkp@bitkey.jp) to add the users in the workhub platform. Users must be created and activated before you use single sign-on.
+In this section, you create a user called Britta Simon at workhub. Work with [workhub support team](mailto:support_work@bitkey.jp) to add the users in the workhub platform. Users must be created and activated before you use single sign-on.
 
 ## Test SSO 
 

articles/azure-vmware/includes/disk-capabilities-of-the-host.md

@@ -3,7 +3,7 @@ title: Disk capabilities of the hosts
 description: Hosts used to build or scale clusters come from an isolated pool of hosts.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 09/18/2022
+ms.date: 09/24/2022
 author: suzizuber
 ms.author: v-szuber
 ---
@@ -19,7 +19,7 @@ Azure VMware Solution clusters are based on hyper-converged, bare-metal infrastr
 | AV36P     |  dual Intel 18 core 2.6 GHz / 3.9 GHz turbo (Cascade Lake) |  768  | 1.5 (Intel Optane Cache) | 19.20 (NVMe) | Selected regions (*) |
 | AV52      |  dual Intel 26 core 2.7 GHz / 4.0 GHz turbo (Cascade Lake) | 1,536  | 1.5 (Intel Optane Cache) | 38.40 (NVMe) | Selected regions (*) |
 
-An Azure VMware cluster requires a minimum number of three hosts. You can only use host of the same type in a single cluster. You can use multiple clusters with different host types in a single Azure VMware Private Cloud.
+An Azure VMware Solution cluster requires a minimum number of three hosts. You can only use host of the same type in a single cluster. You can use multiple clusters with different host types in a single Azure VMware Private Cloud.
 Hosts used to build or scale clusters come from an isolated pool of hosts. Those hosts have passed hardware tests and have had all data securely deleted before being added to a cluster. 
 
 (*) details available via the Azure pricing calculator.

articles/cognitive-services/language-service/concepts/data-limits.md

@@ -46,6 +46,7 @@ The following limit specifies the maximum number of characters that can be in a
 | Feature | Value |
 |------------------------|---------------|
 | Conversation summarization | 7,000 characters as measured by [StringInfo.LengthInTextElements](/dotnet/api/system.globalization.stringinfo.lengthintextelements).|
+| Conversation PII | 40,000 characters as measured by [StringInfo.LengthInTextElements](/dotnet/api/system.globalization.stringinfo.lengthintextelements).|
 | Text Analytics for health | 30,720 characters as measured by [StringInfo.LengthInTextElements](/dotnet/api/system.globalization.stringinfo.lengthintextelements).  | 
 | All other pre-configured features (synchronous) | 5,120 as measured by [StringInfo.LengthInTextElements](/dotnet/api/system.globalization.stringinfo.lengthintextelements). |
 | All other pre-configured features ([asynchronous](use-asynchronously.md))  | 125,000 characters across all submitted documents, as measured by [StringInfo.LengthInTextElements](/dotnet/api/system.globalization.stringinfo.lengthintextelements) (maximum of 25 documents). |

articles/cognitive-services/language-service/custom-named-entity-recognition/includes/roles-for-resource-and-storage.md

@@ -38,3 +38,8 @@ Use the following steps to set the required roles for your Language resource and
 4. Within **Assign access to**, select **Managed identity**. 
 5. Select **Select members**
 6. Select your subscription, and **Language** as the managed identity. You can search for user names in the **Select** field. 
+
+> ![IMPORTANT]
+> If you have a virtual network or private endpoint, be sure to select **Allow Azure services on the trusted services list to access this storage account** in the Azure portal.
+
+

articles/cognitive-services/language-service/custom-text-classification/includes/roles-for-resource-and-storage.md

@@ -38,3 +38,6 @@ Use the following steps to set the required roles for your Language resource and
 4. Within **Assign access to**, select **Managed identity**. 
 5. Select **Select members**
 6. Select your subscription, and **Language** as the managed identity. You can search for user names in the **Select** field. 
+
+> ![IMPORTANT]
+> If you have a virtual network or private endpoint, be sure to select **Allow Azure services on the trusted services list to access this storage account** in the Azure portal.

articles/cognitive-services/language-service/orchestration-workflow/tutorials/connect-services.md

@@ -87,6 +87,7 @@ Now your orchestration project is ready to be used. Any incoming request will be
 ```powershell
 dotnet add package Azure.AI.Language.Conversations
 ```
+Alternatively, you can search for "Azure.AI.Language.Conversations" in the NuGet package manager and install the latest release.
 
 3. In `Program.cs`, replace `{api-key}` and the `{endpoint}` variables. Use the key and endpoint for the Language resource you created earlier. You can find them in the **Keys and Endpoint** tab in your Language resource in Azure.
 
@@ -95,10 +96,11 @@ Uri endpoint = new Uri("{endpoint}");
 AzureKeyCredential credential = new AzureKeyCredential("{api-key}");
 ```
 
-4. Replace the orchestrationProject parameters to **Orchestrator** and **Testing** as below if they are not set already.
+4. Replace the project and deployment parameters to **Orchestrator** and **Testing** as below if they are not set already.
 
 ```csharp
-ConversationsProject orchestrationProject = new ConversationsProject("Orchestrator", "Testing");
+string projectName = "Orchestrator";
+string deploymentName = "Testing";
 ```
 
 5. Run the project or press F5 in Visual Studio. 

articles/load-balancer/TOC.yml

@@ -198,6 +198,8 @@
       href: configure-vm-scale-set-cli.md
   - name: Upgrade from a basic to standard load balancer
     items:
+    - name: Upgrade options and guidance
+      href: load-balancer-basic-upgrade-guidance.md
     - name: Upgrade a basic public load balancer
       href: upgrade-basic-standard.md
     - name: Upgrade an internal load balancer - Outbound connections not required
@@ -214,9 +216,9 @@
       href: load-balancer-multiple-ip-powershell.md
   - name: Move across regions
     items:
-    - name: Public Load Balancer - Portal
+    - name: Public load balancer - Portal
       href: move-across-regions-external-load-balancer-portal.md
-    - name: Public Load Balancer - PowerShell
+    - name: Public load balancer - PowerShell
       href: move-across-regions-external-load-balancer-powershell.md
     - name: Internal load balancer - Portal
       href: move-across-regions-internal-load-balancer-portal.md

articles/load-balancer/index.yml

@@ -34,6 +34,8 @@ landingContent:
             url: https://azure.microsoft.com/updates/?category=networking&query=load%20balancer
           - text: Load Balancer SKUs
             url: skus.md
+          - text: Upgrade guidance from basic to standard Load Balancer
+            url: load-balancer-basic-upgrade-guidance.md
       - linkListType: learn
         links:
           - text: Introduction to Azure Load Balancer