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

v-thepet · v-thepet · commit 2131d6810653 · 2021-11-02T12:43:41.000-07:00
diff --git a/articles/active-directory/enterprise-users/domains-verify-custom-subdomain.md b/articles/active-directory/enterprise-users/domains-verify-custom-subdomain.md
@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: enterprise-users
 ms.workload: identity
 ms.topic: how-to
-ms.date: 09/01/2021
+ms.date: 10/28/2021
 ms.author: curtand
 ms.reviewer: sumitp
 
@@ -23,7 +23,7 @@ ms.collection: M365-identity-device-management
 
 After a root domain is added to Azure Active Directory (Azure AD), all subsequent subdomains added to that root in your Azure AD organization automatically inherit the authentication setting from the root domain. However, if you want to manage domain authentication settings independently from the root domain settings, you can now with the Microsoft Graph API. For example, if you have a federated root domain such as contoso.com, this article can help you verify a subdomain such as child.contoso.com as managed instead of federated.
 
-In the Azure AD portal, when the parent domain is federated and the admin tries to verify a managed subdomain on the **Custom domain names** page, you'll get a 'Failed to add domain' error with the reason "One or more properties contains invalid values". If you try to add this subdomain from the Microsoft 365 admin center, you will receive a similar error. For more information about the error, see [A child domain doesn't inherit parent domain changes in Office 365, Azure, or Intune](/office365/troubleshoot/administration/child-domain-fails-inherit-parent-domain-changes).
+In the Azure AD portal, when the parent domain is federated and the admin tries to verify a managed subdomain on the **Custom domain names** page, you'll get a 'Failed to add domain' error with the reason "One or more properties contains invalid values." If you try to add this subdomain from the Microsoft 365 admin center, you will receive a similar error. For more information about the error, see [A child domain doesn't inherit parent domain changes in Office 365, Azure, or Intune](/office365/troubleshoot/administration/child-domain-fails-inherit-parent-domain-changes).
 
 ## How to verify a custom subdomain
 
diff --git a/articles/active-directory/privileged-identity-management/pim-resource-roles-configure-role-settings.md b/articles/active-directory/privileged-identity-management/pim-resource-roles-configure-role-settings.md
@@ -109,7 +109,7 @@ For more information, see [Multifactor authentication and Privileged Identity Ma
 
 ## Activation maximum duration
 
-Use the **Activation maximum duration** slider to set the maximum time, in hours, that a role stays active before it expires. This value can be from one to 24 hours.
+Use the **Activation maximum duration** slider to set the maximum time, in hours, that a role assignment stays active before it expires. This value can be from one to 24 hours.
 
 ## Require justification
 
diff --git a/articles/chaos-studio/TOC.yml b/articles/chaos-studio/TOC.yml
@@ -44,6 +44,8 @@
     href: chaos-studio-fault-library.md
   - name: Fault providers
     href: chaos-studio-fault-providers.md
+  - name: Preview limitations and known issues
+    href: chaos-studio-limitations.md
   - name: Service limits
     href: chaos-studio-service-limits.md
   - name: REST API documentation
diff --git a/articles/chaos-studio/chaos-studio-limitations.md b/articles/chaos-studio/chaos-studio-limitations.md
@@ -0,0 +1,38 @@
+---
+title: Azure Chaos Studio limitations and known issues
+description: Understand current limitations and known issues when using Azure Chaos Studio.
+services: chaos-studio
+author: johnkemnetz
+ms.topic: overview
+ms.date: 11/02/2021
+ms.author: johnkem
+ms.service: chaos-studio
+---
+
+# Azure Chaos Studio Preview Limitations and Known Issues
+
+During the public preview of Azure Chaos Studio, there are a few limitations and known issues that the team is aware of and working to resolve.
+
+## Limitations 
+
+* For agent-based faults, the machine must have access to the following **HTTPS endpoints**:
+    * http://agentcommunicationservice-frontdoor-canary.trafficmanager.net 
+    * If sending telemetry data to Application Insights, the IPs [in this document](../azure-monitor/app/ip-addresses.md) are also required.
+* If running an experiment that makes use of the Chaos Agent, the VM must run one of the following **operating systems**:
+    * Windows Server 2019, Windows Server 2016, Windows Server 2012, and Windows Server 2012 R2
+    * Redhat Enterprise Linux 8.2, SUSE Enterprise Linux 15 SP2, CentOS 8.2, Debian 10 Buster (with unzip installation required), Oracle Linux 7.8 Ubuntu Server 16.04 LTS, and Ubuntu Server 18.04 LTS
+* The Chaos Agent is not tested against custom Linux distributions, hardened Linux distributions (for example, FIPS or SELinux)
+* The Chaos Studio portal experience has only been tested on the following browsers:
+    * **Windows:** Microsoft Edge, Google Chrome, Firefox
+    * **MacOS:** Safari, Google Chrome, Firefox
+
+## Known issues
+* Onboarding a target in the Azure portal may fail if you navigate away from the Targets view before onboarding completes.
+* When creating an experiment, after clicking **Review + create** there is a delay before the created experiment appears in the experiment list and users must refresh to see the experiment in the list.
+* When picking target resources for an agent-based fault in the experiment designer, it is possible to select virtual machines or virtual machine scale sets with an operating system not supported by the fault selected.
+
+
+## Next steps
+Get started creating and running chaos experiments to improve application resilience with Chaos Studio using the links below.
+- [Create and run your first experiment](chaos-studio-tutorial-service-direct.md)
+- [Learn more about chaos engineering](chaos-studio-chaos-engineering-overview.md)
diff --git a/articles/cognitive-services/Speech-Service/how-to-custom-speech-test-and-train.md b/articles/cognitive-services/Speech-Service/how-to-custom-speech-test-and-train.md
@@ -47,7 +47,7 @@ This table lists accepted data types, when each data type should be used, and th
 | [Audio](#audio-data-for-testing) | Yes<br>Used for visual inspection | 5+ audio files | No | N/A |
 | [Audio + Human-labeled transcripts](#audio--human-labeled-transcript-data-for-trainingtesting) | Yes<br>Used to evaluate accuracy | 0.5-5 hours of audio | Yes | 1-20 hours of audio |
 | [Plain text](#plain-text-data-for-training) | No | N/a | Yes | 1-200 MB of related text |
-| [Structured text](#structured-text-data-for-training-public-preview) (Public Preview) | No | N/a | Yes | Up to 20 classes with up to 2000 items and up to 50,000 training sentences |
+| [Structured text](#structured-text-data-for-training-public-preview) (Public Preview) | No | N/a | Yes | Up to 10 classes with up to 4000 items and up to 50,000 training sentences |
 | [Pronunciation](#pronunciation-data-for-training) | No | N/a | Yes | 1 KB - 1 MB of pronunciation text |
 
 Files should be grouped by type into a dataset and uploaded as a .zip file. Each dataset can only contain a single data type.
@@ -194,7 +194,7 @@ Here is an example of the markdown format:
 ```markdown
 // This is a comment
 
-// Here are three separate lists of items that can be referenced in an example sentence. You can have up to 20 of these
+// Here are three separate lists of items that can be referenced in an example sentence. You can have up to 10 of these
 @ list food =
 - pizza
 - burger
diff --git a/articles/virtual-desktop/azure-stack-hci-faq.yml b/articles/virtual-desktop/azure-stack-hci-faq.yml
@@ -37,7 +37,17 @@ sections:
          Can I use Azure Virtual Desktop with other on-premises infrastructure besides Azure Stack HCI?
         answer: |
           No. Azure Virtual Desktop's on-premises capabilities only extend to session hosts running Azure Stack HCI infrastructure.
-          
+
+      - question: |
+         Is Azure Virtual Desktop an Azure Arc-enabled service?
+        answer: |
+          No, Azure Virtual Desktop is not an Azure Arc-enabled service. It is not supported outside of Azure, in a multi-cloud environment, or on Azure Arc-enabled servers besides Azure Stack HCI virtual machines as described in this technical documentation.
+
+      - question: |
+         Is Azure Virtual Desktop for Azure Stack HCI available in Azure Government?
+        answer: |
+          No, because Azure Stack HCI is not currently available in Azure Government.
+
       - question: |
          Does using Azure Virtual Desktop for Azure Stack HCI mean all my data is stored on-premises?
         answer: |
diff --git a/articles/virtual-desktop/azure-stack-hci-overview.md b/articles/virtual-desktop/azure-stack-hci-overview.md
@@ -60,7 +60,7 @@ We're aware of the following issues affecting the public preview version of Azur
 
 - The Azure Virtual Desktop tab in the Azure portal can't create new virtual machines directly on Azure Stack HCI infrastructure. Instead, admins must create on-premises virtual machines separately, then register them with an Azure Virtual Desktop host pool.
 
-- When connecting to a Windows 10 or 11 Enterprise multi-session virtual desktop, users may see a message that says "activation needed," even if they have an eligible license.
+- When connecting to a Windows 10 or 11 Enterprise multi-session virtual desktop, users may see activation issues, such as a desktop watermark saying "Activate Windows," even if they have an eligible license.
 
 - Azure Virtual Desktop for Azure Stack HCI doesn't currently support host pools containing both cloud and on-premises session hosts. Each host pool in the deployment must have only one type of host pool.
 
diff --git a/articles/virtual-desktop/azure-stack-hci.md b/articles/virtual-desktop/azure-stack-hci.md
@@ -34,20 +34,22 @@ To set up Azure Virtual Desktop for Azure Stack HCI:
 
 1. Create a new host pool with no virtual machines by following the instructions in [Begin the host pool setup process](create-host-pools-azure-marketplace.md#begin-the-host-pool-setup-process). At the end of that section, come back to this article and start on step 2.
 
-2. Follow the instructions in [Workspace information](create-host-pools-azure-marketplace.md#workspace-information) to create a workspace for yourself.
+2. Configure the newly created host pool to be a validation host pool by following the steps in [Define your host pool as a validation host pool](create-validation-host-pool.md#define-your-host-pool-as-a-validation-host-pool) to enable the Validation environment property.
 
-3. Deploy a new virtual machine on your Azure Stack HCI infrastructure by following the instructions in [Create a new VM](/azure-stack/hci/manage/vm#create-a-new-vm). Deploy a VM with a supported OS and join it to a domain.
+3. Follow the instructions in [Workspace information](create-host-pools-azure-marketplace.md#workspace-information) to create a workspace for yourself.
+
+4. Deploy a new virtual machine on your Azure Stack HCI infrastructure by following the instructions in [Create a new VM](/azure-stack/hci/manage/vm#create-a-new-vm). Deploy a VM with a supported OS and join it to a domain.
 
    >[!NOTE]
    >Install the Remote Desktop Session Host (RDSH) role if the VM is running a Windows Server OS.
 
-4. Enable Azure to manage the new virtual machine through Azure Arc by installing the Connected Machine agent to it. Follow the directions in [Connect hybrid machines with Azure Arc-enabled servers](../azure-arc/servers/learn/quick-enable-hybrid-vm.md) to install the Windows agent to the virtual machine.
+5. Enable Azure to manage the new virtual machine through Azure Arc by installing the Connected Machine agent to it. Follow the directions in [Connect hybrid machines with Azure Arc-enabled servers](../azure-arc/servers/learn/quick-enable-hybrid-vm.md) to install the Windows agent to the virtual machine.
 
-5. Add the virtual machine to the Azure Virtual Desktop host pool you created earlier by installing the [Azure Virtual Desktop Agent](agent-overview.md). After that, follow the instructions in [Register the VMs to the Azure Virtual Desktop host pool](create-host-pools-powershell.md#register-the-virtual-machines-to-the-azure-virtual-desktop-host-pool) to register the VM to the Azure Virtual Desktop service.
+6. Add the virtual machine to the Azure Virtual Desktop host pool you created earlier by installing the [Azure Virtual Desktop Agent](agent-overview.md). After that, follow the instructions in [Register the VMs to the Azure Virtual Desktop host pool](create-host-pools-powershell.md#register-the-virtual-machines-to-the-azure-virtual-desktop-host-pool) to register the VM to the Azure Virtual Desktop service.
 
-6. Follow the directions in [Create app groups and manage user assignments](manage-app-groups.md) to create an app group for testing and assign user access to it.
+7. Follow the directions in [Create app groups and manage user assignments](manage-app-groups.md) to create an app group for testing and assign user access to it.
 
-7. Go to [the web client](./user-documentation/connect-web.md) and grant your users access to the new deployment.
+8. Go to [the web client](./user-documentation/connect-web.md) and grant your users access to the new deployment.
 
 ## Optional configurations
 
