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

Author: HeidiSteen

articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-configure-authentication.md

@@ -98,8 +98,8 @@ The application uses the [Implicit Grant Flow](../../develop/v2-oauth2-implicit-
 
 1. Replace the following values with the values from the Azure portal:
     - Find the `Enter_the_Application_Id_Here` value and replace it with the **Application ID (clientId)** of the app you registered in the Microsoft Entra admin center.
-    - In **Authority**, find `Enter_the_Tenant_Subdomain_Here` and replace it with the subdomain of your tenant. For example, if your tenant primary domain is *caseyjensen@onmicrosoft.com*, the value you should enter is *casyjensen*.
-1. Save the file.
+      - In **Authority**, find `Enter_the_Tenant_Subdomain_Here` and replace it with the subdomain of your tenant. For example, if your tenant primary domain is `contoso.onmicrosoft.com`, use `contoso`. If you don't have your tenant name, [learn how to read your tenant details](how-to-create-customer-tenant-portal.md#get-the-customer-tenant-details).
+2. Save the file.
 
 ## Adding code to the redirection file
 

articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-prepare-tenant.md

@@ -18,7 +18,7 @@ ms.date: 06/09/2023
 
 This tutorial series demonstrates how to build a vanilla JavaScript single-page application (SPA) and prepare it for authentication using the Microsoft Entra admin center. You'll use the [Microsoft Authentication Library for JavaScript](/javascript/api/overview/msal-overview) library to authenticate your app with your Azure Active Directory (Azure AD) for customers tenant. Finally, you'll run the application and test the sign-in and sign-out experiences.
 
-In this tutorial, you'll;
+In this tutorial;
 
 > [!div class="checklist"]
 > * Register a SPA in the Microsoft Entra admin center, and record its identifiers

articles/active-directory/external-identities/customers/how-to-single-page-application-react-prepare-app.md

@@ -150,9 +150,10 @@ Identity related **npm** packages must be installed in the project to enable use
     // };
     ```
 
-1. Replace the following values with the values from the Azure admin center:
-    - Replace `Enter_the_Application_Id_Here` with the **Application (client) ID** value that was recorded earlier from the **Overview** page of the registered application.
-    - In **Authority**, find `Enter_the_Tenant_Subdomain_Here` and replace it with the subdomain of your tenant. For example, if your tenant primary domain is *[email protected]*, the value you should enter is *casyjensen*.
+1. Replace the following values with the values from the Azure portal:
+    - Find the `Enter_the_Application_Id_Here` value and replace it with the **Application ID (clientId)** of the app you registered in the Microsoft Entra admin center.
+    - In **Authority**, find `Enter_the_Tenant_Subdomain_Here` and replace it with the subdomain of your tenant. For example, if your tenant primary domain is `contoso.onmicrosoft.com`, use `contoso`. If you don't have your tenant name, [learn how to read your tenant details](how-to-create-customer-tenant-portal.md#get-the-customer-tenant-details).
+2. Save the file.
 
 ## Modify *index.js* to include the authentication provider
 

articles/azure-resource-manager/management/azure-services-resource-providers.md

@@ -2,8 +2,10 @@
 title: Resource providers by Azure services
 description: Lists all resource provider namespaces for Azure Resource Manager and shows the Azure service for that namespace.
 ms.topic: conceptual
-ms.date: 02/28/2023
+ms.date: 07/14/2023
 ms.custom: ignite-2022, devx-track-arm-template
+content_well_notification: 
+  - AI-contribution
 ---
 
 # Resource providers for Azure services
@@ -186,26 +188,26 @@ The resources providers that are marked with **- registered** are registered by
 
 ## Registration
 
-The resources providers in the preceding section that are marked with **- registered** are registered by default for your subscription. To use the other resource providers, you must [register them](resource-providers-and-types.md). However, many resource providers are registered for you when you take certain actions. For example, if you create a resource through the portal, the portal automatically registers any unregistered resource providers that are needed. When deploy resources through an [Azure Resource Manager template](../templates/overview.md), any required resource providers are also registered.
+Resource providers marked with **- registered** in the previous section are automatically registered for your subscription. For other resource providers, you need to [register them](resource-providers-and-types.md). However, many resource providers are registered automatically when you perform specific actions. For example, when you create resources through the portal or by deploying an [Azure Resource Manager template](../templates/overview.md), Azure Resource Manager automatically registers any required unregistered resource providers.
 
 > [!IMPORTANT]
-> Only register a resource provider when you're ready to use it. The registration step enables you to maintain least privileges within your subscription. A malicious user can't use resource providers that aren't registered.
+> Register a resource provider only when you're ready to use it. This registration step helps maintain least privileges within your subscription. A malicious user can't use unregistered resource providers.
 >
-> When you register resource providers that aren't needed, you may see apps in your Azure Active Directory tenant that you don't recognize. Microsoft adds the app for a resource provider when you register it. These applications are typically added by Windows Azure Service Management API. To avoid having unnecessary apps in your tenant, only register resource providers that are needed.
+> Registering unnecessary resource providers may result in unrecognized apps appearing in your Azure Active Directory tenant. Microsoft adds the app for a resource provider when you register it. These apps are typically added by the Windows Azure Service Management API. To prevent unnecessary apps in your tenant, only register needed resource providers.
 
 ## Find resource provider
 
-If you have existing infrastructure in Azure, but aren't sure which resource provider is used, you can use either Azure CLI or PowerShell to find the resource provider. Specify the name of the resource group that contains the resources to find.
+To identify resource providers used for your existing Azure infrastructure, list the deployed resources. Specify the resource group containing the resources.
 
 The following example uses Azure CLI:
 
 ```azurecli-interactive
-az resource list -g examplegroup
+az resource list --resource-group examplegroup
 ```
 
 The results include the resource type. The resource provider namespace is the first part of the resource type. The following example shows the **Microsoft.KeyVault** resource provider.
 
-```json
+```output
 [
   {
     ...
@@ -222,13 +224,37 @@ Get-AzResource -ResourceGroupName examplegroup
 
 The results include the resource type. The resource provider namespace is the first part of the resource type. The following example shows the **Microsoft.KeyVault** resource provider.
 
-```azurepowershell
+```output
 Name              : examplekey
 ResourceGroupName : examplegroup
 ResourceType      : Microsoft.KeyVault/vaults
 ...
 ```
 
+The following example uses Python:
+
+```python
+import os
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.resource import ResourceManagementClient
+
+subscription_id = os.environ["AZURE_SUBSCRIPTION_ID"]
+credential = DefaultAzureCredential()
+resource_client = ResourceManagementClient(credential, subscription_id)
+
+resource_group_name = "examplegroup"
+resources = resource_client.resources.list_by_resource_group(resource_group_name)
+
+for resource in resources:
+    print(resource.type)
+```
+
+The results list the resource type. The resource provider namespace is the first part of the resource type. The following example shows the **Microsoft.KeyVault** resource provider.
+
+```output
+Microsoft.KeyVault/vaults
+```
+
 ## Next steps
 
 For more information about resource providers, including how to register a resource provider, see [Azure resource providers and types](resource-providers-and-types.md).

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: 02/28/2023
+ms.date: 07/14/2023
 ms.custom: "references_regions, engagement-fy23"
 ---
 
@@ -60,6 +60,7 @@ Azure NetApp Files datastores for Azure VMware Solution are currently supported
 * Japan West
 * North Central US
 * North Europe
+* Qatar Central
 * South Africa North
 * South Central US
 * Southeast Asia
@@ -71,7 +72,7 @@ Azure NetApp Files datastores for Azure VMware Solution are currently supported
 * West Europe 
 * West US
 * West US 2
-
+* West US 3
 
 ## Performance best practices
 

articles/chaos-studio/chaos-studio-fault-library.md

@@ -349,7 +349,7 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 ```
 
 ### Limitations
-* **Windows**: Service-friendly names aren't supported. Use `sc.exe query` in the command prompt to explore service names.
+* **Windows**: Display names for services aren't supported. Use `sc.exe query` in the command prompt to explore service names.
 * **Linux**: Other service types besides systemd, like sysvinit, aren't supported.
 
 ## Time change
@@ -403,7 +403,7 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 | Prerequisites | None. |
 | Urn | urn:csci:microsoft:agent:killProcess/1.0 |
 | Parameters (key, value) |  |
-| processName | Name of a process running on a VM (without the .exe). |
+| processName | Name of a process to continuously kill (without the .exe). The process does not need to be running when the fault begins executing. |
 | killIntervalInMilliseconds | Amount of time the fault waits in between successive kill attempts in milliseconds. |
 | virtualMachineScaleSetInstances | An array of instance IDs when this fault is applied to a virtual machine scale set. Required for virtual machine scale sets. |
 
@@ -536,6 +536,11 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 }
 ```
 
+### Limitations
+
+* The agent-based network faults currently only support IPv4 addresses.
+
+
 ## Network disconnect
 
 | Property | Value |
@@ -580,8 +585,11 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 }
 ```
 
-> [!WARNING]
-> The network disconnect fault only affects new connections. Existing *active* connections continue to persist. You can restart the service or process to force connections to break.
+### Limitations
+
+* The agent-based network faults currently only support IPv4 addresses.
+* The network disconnect fault only affects new connections. Existing active connections continue to persist. You can restart the service or process to force connections to break.
+* On Windows, the network disconnect fault currently only works with TCP or UDP packets.
 
 ## Network disconnect with firewall rule
 
@@ -627,6 +635,63 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 }
 ```
 
+### Limitations
+
+* The agent-based network faults currently only support IPv4 addresses.
+
+## Network packet loss
+
+| Property | Value |
+|-|-|
+| Capability name | NetworkPacketLoss-1.0 |
+| Target type | Microsoft-Agent |
+| Supported OS types | Windows, Linux |
+| Description | Introduces packet loss for outbound traffic at a specified rate, between 0.0 (no packets lost) and 1.0 (all packets lost). This can help simulate scenarios like network congestion or network hardware issues. |
+| Prerequisites | Agent must run as administrator. If the agent is installed as a VM extension, it runs as administrator by default. |
+| Urn | urn:csci:microsoft:agent:networkPacketLoss/1.0 |
+| Parameters (key, value) |  |
+| lossRate | The rate at which packets matching the destination filters will be lost, ranging from 0.0 to 1.0. |
+| virtualMachineScaleSetInstances | An array of instance IDs when this fault is applied to a virtual machine scale set. Required for virtual machine scale sets. |
+| destinationFilters | Delimited JSON array of packet filters (parameters below) that define which outbound packets to target for fault injection. Maximum of three.|
+| address | IP address that indicates the start of the IP range. |
+| subnetMask | Subnet mask for the IP address range. |
+| portLow | (Optional) Port number of the start of the port range. |
+| portHigh | (Optional) Port number of the end of the port range. |
+
+### Sample JSON
+
+```json
+{
+  "name": "branchOne",
+  "actions": [
+    {
+      "type": "continuous",
+      "name": "urn:csci:microsoft:agent:networkPacketLoss/1.0",
+      "parameters": [
+            {
+                "key": "destinationFilters",
+                "value": "[{\"address\":\"23.45.229.97\",\"subnetMask\":\"255.255.255.224\",\"portLow\":5000,\"portHigh\":5200}]"
+            },
+            {
+                "key": "lossRate",
+                "value": "0.5"
+            },
+            {
+                "key": "virtualMachineScaleSetInstances",
+                "value": "[0,1,2]"
+            }
+        ],
+      "duration": "PT10M",
+      "selectorid": "myResources"
+    }
+  ]
+}
+```
+
+### Limitations
+
+* The agent-based network faults currently only support IPv4 addresses.
+
 ## Azure Resource Manager virtual machine shutdown
 | Property | Value |
 |-|-|
@@ -663,7 +728,7 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 
 ## Azure Resource Manager virtual machine scale set instance shutdown
 
-This fault has two available versions that you can use, Version 1.0 and Version 2.0.
+This fault has two available versions that you can use, Version 1.0 and Version 2.0. The main difference is that Version 2.0 allows you to filter by availability zones, only shutting down instances within a specified zone or zones.
 
 ### Version 1.0
 
@@ -864,7 +929,7 @@ Currently, only virtual machine scale sets configured with the **Uniform** orche
       "parameters": [
         {
             "key": "jsonSpec",
-            "value": "{\"action\":\"pod-failure\",\"mode\":\"one\",\"duration\":\"30s\",\"selector\":{\"labelSelectors\":{\"app.kubernetes.io\/component\":\"tikv\"}}}"
+            "value": "{\"action\":\"pod-failure\",\"mode\":\"one\",\"selector\":{\"labelSelectors\":{\"app.kubernetes.io\/component\":\"tikv\"}}}"
         }
     ],
       "selectorid": "myResources"
@@ -932,7 +997,7 @@ Currently, only virtual machine scale sets configured with the **Uniform** orche
       "parameters": [
         {
             "key": "jsonSpec",
-            "value": "{\"action\":\"latency\",\"mode\":\"one\",\"selector\":{\"labelSelectors\":{\"app\":\"etcd\"}},\"volumePath\":\"\/var\/run\/etcd\",\"path\":\"\/var\/run\/etcd\/**\/*\",\"delay\":\"100ms\",\"percent\":50,\"duration\":\"400s\"}"
+            "value": "{\"action\":\"latency\",\"mode\":\"one\",\"selector\":{\"labelSelectors\":{\"app\":\"etcd\"}},\"volumePath\":\"\/var\/run\/etcd\",\"path\":\"\/var\/run\/etcd\/**\/*\",\"delay\":\"100ms\",\"percent\":50}"
         }
     ],
       "selectorid": "myResources"
@@ -1034,7 +1099,7 @@ Currently, only virtual machine scale sets configured with the **Uniform** orche
       "parameters": [
         {
             "key": "jsonSpec",
-            "value": "{\"mode\":\"all\",\"selector\":{\"labelSelectors\":{\"app\":\"nginx\"}},\"target\":\"Request\",\"port\":80,\"method\":\"GET\",\"path\":\"\/api\",\"abort\":true,\"duration\":\"5m\",\"scheduler\":{\"cron\":\"@every 10m\"}}"
+            "value": "{\"mode\":\"all\",\"selector\":{\"labelSelectors\":{\"app\":\"nginx\"}},\"target\":\"Request\",\"port\":80,\"method\":\"GET\",\"path\":\"\/api\",\"abort\":true,\"scheduler\":{\"cron\":\"@every 10m\"}}"
         }
     ],
       "selectorid": "myResources"
@@ -1089,8 +1154,8 @@ Currently, only virtual machine scale sets configured with the **Uniform** orche
 | Parameters (key, value) |  |
 | name | A unique name for the security rule that's created. The fault fails if another rule already exists on the NSG with the same name. Must begin with a letter or number. Must end with a letter, number, or underscore. May contain only letters, numbers, underscores, periods, or hyphens. |
 | protocol | Protocol for the security rule. Must be Any, TCP, UDP, or ICMP. |
-| sourceAddresses | A string that represents a JSON-delimited array of CIDR-formatted IP addresses. Can also be a service tag name for an inbound rule, for example, `AppService`. An asterisk `*` can also be used to match all source IPs. |
-| destinationAddresses | A string that represents a JSON-delimited array of CIDR-formatted IP addresses. Can also be a service tag name for an outbound rule, for example, `AppService`. An asterisk `*` can also be used to match all destination IPs. |
+| sourceAddresses | A string that represents a JSON-delimited array of CIDR-formatted IP addresses. Can also be a [service tag name](../virtual-network/service-tags-overview.md) for an inbound rule, for example, `AppService`. An asterisk `*` can also be used to match all source IPs. |
+| destinationAddresses | A string that represents a JSON-delimited array of CIDR-formatted IP addresses. Can also be a [service tag name](../virtual-network/service-tags-overview.md) for an outbound rule, for example, `AppService`. An asterisk `*` can also be used to match all destination IPs. |
 | action | Security group access type. Must be either Allow or Deny. |
 | destinationPortRanges | A string that represents a JSON-delimited array of single ports and/or port ranges, such as 80 or 1024-65535. |
 | sourcePortRanges | A string that represents a JSON-delimited array of single ports and/or port ranges, such as 80 or 1024-65535. |
@@ -1456,3 +1521,32 @@ Currently, only virtual machine scale sets configured with the **Uniform** orche
   ]
 }
 ```
+
+## App Service Stop
+	
+| Property  | Value |
+| ---- | --- |
+| Capability name | Stop-1.0 |
+| Target type | Microsoft-AppService |
+| Description | Stops the targeted App Service applications, then restarts them at the end of the fault duration. This applies to resources of the "Microsoft.Web/sites" type, including App Service, API Apps, Mobile Apps, and Azure Functions. |
+| Prerequisites | None. |
+| Urn | urn:csci:microsoft:appService:stop/1.0 |
+| Fault type | Continuous. |
+| Parameters (key, value) | None. |
+
+### Sample JSON
+
+```json
+{
+  "name": "branchOne",
+  "actions": [
+    {
+      "type": "continuous",
+      "name": "urn:csci:microsoft:appService:stop/1.0",
+      "duration": "PT10M",
+      "parameters":[],
+      "selectorid": "myResources"
+    }
+  ]
+}
+```

articles/chaos-studio/chaos-studio-fault-providers.md

@@ -27,3 +27,4 @@ The following table lists the supported resource types for faults, the target ty
 | Microsoft.Insights/autoscalesettings (service-direct)            | Microsoft-AutoScaleSettings               | Web Plan Contributor                        |
 | Microsoft.KeyVault/vaults (service-direct)                       | Microsoft-KeyVault                        | Azure Key Vault Contributor                       |
 | Microsoft.Network/networkSecurityGroups (service-direct)         | Microsoft-NetworkSecurityGroup            | Network Contributor                         |
+| Microsoft.Web/sites (service-direct)                             | Microsoft-AppService                      | Website Contributor                         |

articles/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 02/16/2023
+ms.date: 07/11/2023
 ms.author: alkohli
 # Customer intent: As an IT admin, I need to understand how to deploy and configure Azure Kubernetes service on Azure Stack Edge.
 ---
@@ -48,7 +48,7 @@ Depending on the workloads you intend to deploy, you may need to ensure the foll
 
    ```azurepowershell
    az login
-   az ad sp show --id 'bc313c14-387c-4e7d-a58e-70417303ee3b' --query id -o tsv
+   az ad sp show --id bc313c14-387c-4e7d-a58e-70417303ee3b --query id -o tsv
    ```
 
    Here's a sample output using the Azure CLI. You can run the same commands via the Cloud Shell in the Azure portal.