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

roygara · roygara · commit 844e20e3707d · 2023-01-25T10:18:44.000-08:00
diff --git a/articles/active-directory/saas-apps/appdynamics-tutorial.md b/articles/active-directory/saas-apps/appdynamics-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 11/21/2022
+ms.date: 01/25/2023
 ms.author: jeedes
 ---
 # Tutorial: Azure Active Directory integration with AppDynamics
@@ -73,14 +73,17 @@ 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 **Sign on URL** text box, type a URL using the following pattern:
-    `https://<companyname>.saas.appdynamics.com?accountName=<companyname>`
-
-    b. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
+    a. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
     `https://<companyname>.saas.appdynamics.com/controller`
 
+    b. In the **Reply URL (Assertion Consumer Service URL)** text box, type a URL using the following pattern:
+    `https://<companyname>.saas.appdynamics.com/controller/saml-auth?accountName=<companyname>`
+
+    c. In the **Sign on URL** text box, type a URL using the following pattern:
+    `https://<companyname>.saas.appdynamics.com/?accountName=<companyname>`
+
     > [!NOTE]
-    > These values are not real. Update these values with the actual Sign on URL and Identifier. Contact [AppDynamics Client support team](https://www.appdynamics.com/support/) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+    > These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [AppDynamics Client support team](https://www.appdynamics.com/support/) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 4. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, click **Download** to download the **Certificate (Base64)** from the given options as per your requirement and save it on your computer.
 
@@ -156,4 +159,4 @@ In this section, you test your Azure AD single sign-on configuration with follow
 
 ## Next steps
 
-Once you configure AppDynamics you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).
+Once you configure AppDynamics you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).
diff --git a/articles/active-directory/saas-apps/slack-tutorial.md b/articles/active-directory/saas-apps/slack-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 11/21/2022
+ms.date: 01/25/2023
 ms.author: jeedes
 ---
 
@@ -38,7 +38,7 @@ To get started, you need the following items:
 
 In this tutorial, you configure and test Azure AD SSO in a test environment.
 
-* Slack supports **SP** initiated SSO.
+* Slack supports **SP (service provider)** initiated SSO.
 * Slack supports **Just In Time** user provisioning.
 * Slack supports [**Automated** user provisioning](./slack-provisioning-tutorial.md).
 
@@ -56,8 +56,6 @@ To configure the integration of Slack into Azure AD, you need to add Slack from
 1. In the **Add from the gallery** section, type **Slack** in the search box.
 1. Select **Slack** 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, as well as walk through the SSO configuration as well. You can learn more about O365 wizards [here](/microsoft-365/admin/misc/azure-ad-setup-guides?view=o365-worldwide&preserve-view=true).
 
 ## Configure and test Azure AD SSO for Slack
@@ -91,7 +89,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
     b. In the **Identifier (Entity ID)** text box, type the URL:
     `https://slack.com`
 	
-    c. For **Reply URL**, enter one of the following URL pattern:
+    c. For **Reply URL**, enter one of the following URL patterns:
     
 	| Reply URL|
 	|----------|
@@ -162,7 +160,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 	![Setup configuration](common/setup-sso.png)
 
-3. If you want to setup Slack manually, in a different web browser window, sign in to your Slack company site as an administrator.
+3. If you want to set up Slack manually, in a different web browser window, sign in to your Slack company site as an administrator.
 
 2. click on your workspace name in the top left, then go to **Settings & administration** -> **Workspace settings**.
 
diff --git a/articles/active-directory/saas-apps/valid8me-tutorial.md b/articles/active-directory/saas-apps/valid8me-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 11/21/2022
+ms.date: 01/25/2023
 ms.author: jeedes
 
 ---
@@ -78,15 +78,10 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 1. On the **Basic SAML Configuration** section, the user does not have to perform any step as the app is already pre-integrated with Azure.
 
-1. Click **Set additional URLs** and perform the following step, if you wish to configure the application in **SP** initiated mode:
+1. If you wish to configure the application in **SP** initiated mode:
 
-    In the **Sign on URL** textbox, type a URL using one of the following patterns:
-
-    | **Sign on URL** |
-    |------------|
-    | `https://login.valid8me.com` |
-    | `https://login.valid8me.com/?idp=https://sts.windows.net/${TenantID}/` |
-    | `https://<<client_name>>.valid8me.com` |
+    In the **Sign on URL (Optional)** text box, type a URL using the following pattern:
+    `https://login.valid8me.com/?idp=https://sts.windows.net/${TenantID}/`
 
     > [!Note]
     > This value is not real. Update this value with the actual Sign on URL. Contact [valid8Me support team](mailto:support@valid8me.com) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
diff --git a/articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md b/articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md
@@ -3,7 +3,7 @@ title: Attach Azure NetApp Files datastores to Azure VMware Solution hosts
 description: Learn how to create Azure NetApp Files-based NFS datastores for Azure VMware Solution hosts.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 01/13/2023
+ms.date: 01/25/2023
 ms.custom: references_regions
 ---
 
@@ -90,7 +90,7 @@ Under **Manage**, select **Storage**.
     :::image type="content" source="media/attach-netapp-files-to-cloud/connect-netapp-files-portal-experience-1.png" alt-text="Image shows the navigation to Connect Azure NetApp Files volume pop-up window." lightbox="media/attach-netapp-files-to-cloud/connect-netapp-files-portal-experience-1.png":::
 
 1. Verify the protocol is NFS. You'll need to verify the virtual network and subnet to ensure connectivity to the Azure VMware Solution private cloud.
-1. Under **Associated cluster**, select the **Client cluster** to associate the NFS volume as a datastore
+1. Under **Associated cluster**, in the **Client cluster** field, select one or more clusters to associate the volume as a datastore.
 1. Under **Data store**, create a personalized name for your **Datastore name**.
     1. When the datastore is created, you should see all of your datastores in the **Storage**.
     2. You'll also notice that the NFS datastores are added in vCenter.
@@ -208,3 +208,7 @@ Now that you've attached a datastore on Azure NetApp Files-based NFS volume to y
 - **How are the datastores charged, is there an additional charge?**
 
     Azure NetApp Files NFS volumes that are used as datastores will be billed following the [capacity pool based billing model](../azure-netapp-files/azure-netapp-files-cost-model.md). Billing will depend on the service level. There's no extra charge for using Azure NetApp Files NFS volumes as datastores.
+
+- **Can a single Azure NetApp Files datastore be added to multiple clusters within the same Azure VMware Solution SDDC?**
+
+    Yes, you can select multiple datastores at the time of datastore creation. Additional clusters may be added or removed after the initial creation as well.
