Merge pull request #203956 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/devices/concept-azure-ad-register.md

@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
 ---
 # Azure AD registered devices
 
-The goal of Azure AD registered devices is to provide your users with support for bring your own device (BYOD) or mobile device scenarios. In these scenarios, a user can access your organization’s resources using a personal device.
+The goal of Azure AD registered - also known as Workplace joined - devices is to provide your users with support for bring your own device (BYOD) or mobile device scenarios. In these scenarios, a user can access your organization’s resources using a personal device.
 
 | Azure AD Registered | Description |
 | --- | --- |

articles/active-directory/devices/howto-hybrid-join-downlevel.md

@@ -21,6 +21,7 @@ If some of your domain-joined devices are Windows [downlevel devices](hybrid-azu
 
 - Configure the local intranet settings for device registration
 - Install Microsoft Workplace Join for Windows downlevel computers
+- Need AD FS (for federated domains) or Seamless SSO configured (for managed domains).
 
 > [!NOTE]
 > Windows 7 support ended on January 14, 2020. For more information, [Support for Windows 7 has ended](https://support.microsoft.com/en-us/help/4057281/windows-7-support-ended-on-january-14-2020).

articles/active-directory/managed-identities-azure-resources/how-to-view-associated-resources-for-an-identity.md

@@ -64,7 +64,7 @@ https://management.azure.com/subscriptions/{resourceID of user-assigned identity
 
 | Parameter   | Example  |Description  |
 |---|---|---|
-| $filter  |  ```'type' eq 'microsoft.cognitiveservices/account' and contains(name, 'test')``` |  An OData expression that allows you to filter any of the available fields: name, type, resourceGroup, subscriptionId, subscriptionDisplayName, subscriptionId, subscriptionDisplayName<br/><br/>The following operations are supported: ```and```, ```or```, ```eq``` and ```contains``` |
+| $filter  |  ```'type' eq 'microsoft.cognitiveservices/account' and contains(name, 'test')``` |  An OData expression that allows you to filter any of the available fields: name, type, resourceGroup, subscriptionId, subscriptionDisplayName<br/><br/>The following operations are supported: ```and```, ```or```, ```eq``` and ```contains``` |
 |  $orderby |  ```name asc``` |  An OData expression that allows you to order by any of the available fields |
 |  $skip |  50 |  The number of items you want to skip while paging through the results. |
 | $top  |  10 | The number of resources to return. 0 will return only a count of the resources.  |

articles/azure-functions/functions-manually-run-non-http.md

@@ -63,6 +63,9 @@ Open Postman and follow these steps:
 
     :::image type="content" source="./media/functions-manually-run-non-http/functions-manually-run-non-http-body.png" alt-text="Postman body settings." border="true":::
 
+   > [!NOTE]
+   > If you don't want to pass data into the function, you must still pass an empty dictionary `{}` as the body of the POST request.
+
 1. Select **Send**.
 
     :::image type="content" source="./media/functions-manually-run-non-http/functions-manually-run-non-http-send.png" alt-text="Send a request with Postman." border="true":::

articles/azure-monitor/app/availability-overview.md

@@ -17,7 +17,7 @@ You can set up availability tests for any HTTP or HTTPS endpoint that's accessib
 There are four types of availability tests:
 
 * [URL ping test (classic)](monitor-web-app-availability.md): You can create this simple test through the portal to validate whether an endpoint is responding and measure performance associated with that response. You can also set custom success criteria coupled with more advanced features, like parsing dependent requests and allowing for retries.
-* [Standard test (Preview)](availability-standard-tests.md): This single request test is similar to the URL ping test. It includes SSL certificate validity, proactive lifetime check, HTTP request verb (for example `GET`, `HEAD`, or `POST`), custom headers, and custom data associated with your HTTP request.
+* [Standard test](availability-standard-tests.md): This single request test is similar to the URL ping test. It includes SSL certificate validity, proactive lifetime check, HTTP request verb (for example `GET`, `HEAD`, or `POST`), custom headers, and custom data associated with your HTTP request.
 * [Multi-step web test (classic)](availability-multistep.md): You can play back this recording of a sequence of web requests to test more complex scenarios. Multi-step web tests are created in Visual Studio Enterprise and uploaded to the portal, where you can run them.
 * [Custom TrackAvailability test](availability-azure-functions.md): If you decide to create a custom application to run availability tests, you can use the [TrackAvailability()](/dotnet/api/microsoft.applicationinsights.telemetryclient.trackavailability) method to send the results to Application Insights.
 
@@ -36,7 +36,8 @@ See the dedicated [troubleshooting article](https://docs.microsoft.com/troublesh
 ## Next steps
 
 * [Availability alerts](availability-alerts.md)
-* [Multi-step web tests](availability-multistep.md)
 * [URL tests](monitor-web-app-availability.md)
+* [Standard Tests](availability-standard-tests.md)
+* [Multi-step web tests](availability-multistep.md)
 * [Create and run custom availability tests using Azure Functions](availability-azure-functions.md)
 * [Web Tests Azure Resource Manager template](/azure/templates/microsoft.insights/webtests?tabs=json)

articles/azure-vmware/enable-public-ip-nsx-edge.md

@@ -122,7 +122,7 @@ For example, the following rule is set to Match External Address, and this setti
 
 If **Match Internal Address** was specified, the destination would be the internal or private IP address of the VM. 
 For more information on the NSX-T Gateway Firewall see the [NSX-T Gateway Firewall Administration Guide]( https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-A52E1A6F-F27D-41D9-9493-E3A75EC35481.html)
-The Distributed Firewall could be used to filter traffic to VMs. This feature is outside the scope of this document. For more information, see [NSX-T Distributed Firewall Administration Guide]( https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-6AB240DB-949C-4E95-A9A7-4AC6EF5E3036.html)git status.
+The Distributed Firewall could be used to filter traffic to VMs. This feature is outside the scope of this document. For more information, see [NSX-T Distributed Firewall Administration Guide]( https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-6AB240DB-949C-4E95-A9A7-4AC6EF5E3036.html).
 
 ## Next steps 
 [Internet connectivity design considerations (Preview)](concepts-design-public-internet-access.md)

articles/cognitive-services/Anomaly-Detector/toc.yml

@@ -26,9 +26,9 @@
     - name: Jupyter Notebook
       href: https://github.com/Azure-Samples/AnomalyDetector/tree/master/ipython-notebook
     - name: Azure samples (univariate)
-      href: https://github.com/Azure-Samples/AnomalyDetector/tree/master/quickstarts
+      href: https://github.com/Azure-Samples/AnomalyDetector/tree/master/samples-univariate
     - name: Azure samples (multivariate)
-      href: https://github.com/Azure-Samples/AnomalyDetector/tree/master/quickstarts-multivariate
+      href: https://github.com/Azure-Samples/AnomalyDetector/tree/master/samples-multivariate
 - name: How-to guides
   items:
     - name: Identify anomalies in your data (univariate)

articles/cosmos-db/cassandra/access-data-spring-data-app.md

@@ -51,7 +51,7 @@ The following procedure configures the test application.
    ```     
 
     > [!NOTE]    
-    > Although the usage described below is identical for both Java version 3 and version 4 samples above, the way in which they have been implemented in order to include custom retry and load balancing policies is different. We recommend reviewing the code to understand how to implement custom policies if you are making changes to an existing spring java application.  
+    > Although the usage described below is identical for both Java version 3 and version 4 samples above, the way in which they have been implemented in order to include custom retry and load balancing policies is different. We recommend reviewing the code to understand how to implement custom policies if you are making changes to an existing Spring Java application.  
 
 1. Locate the *application.properties* file in the *resources* directory of the sample project, or create the file if it does not already exist.
 
@@ -153,4 +153,4 @@ For more information about using Azure with Java, see the [Azure for Java Develo
 [COSMOSDB04]: media/access-data-spring-data-app/create-cosmos-db-04.png
 [COSMOSDB05]: media/access-data-spring-data-app/create-cosmos-db-05.png
 [COSMOSDB05-1]: media/access-data-spring-data-app/create-cosmos-db-05-1.png
-[COSMOSDB06]: media/access-data-spring-data-app/create-cosmos-db-06.png
+[COSMOSDB06]: media/access-data-spring-data-app/create-cosmos-db-06.png

articles/cosmos-db/table/create-table-java.md

@@ -219,7 +219,7 @@ The connection string for your Cosmos DB account is considered an app secret and
 
 ## 4 - Include the azure-data-tables package
 
-To access the Cosmos DB Tables API from a java application, include the [azure-data-tables](https://search.maven.org/artifact/com.azure/azure-data-tables) package.
+To access the Cosmos DB Tables API from a Java application, include the [azure-data-tables](https://search.maven.org/artifact/com.azure/azure-data-tables) package.
 
 ```xml
 <dependency>

articles/defender-for-cloud/alerts-reference.md

@@ -378,7 +378,7 @@ Microsoft Defender for Containers provides security alerts on the cluster level
 
 <sup><a name="footnote1"></a>1</sup>: **Preview for non-AKS clusters**: This alert is generally available for AKS clusters, but it is in preview for other environments, such as Azure Arc, EKS and GKE.
 
-<sup><a name="footnote2"></a>2</sup>: **Limitations on GKE clusters**: GKE uses a Kuberenetes audit policy that doesn't support all alert types. As a result, this security alert, which is based on Kubernetes audit events, are not supported for GKE clusters.
+<sup><a name="footnote2"></a>2</sup>: **Limitations on GKE clusters**: GKE uses a Kuberenetes audit policy that doesn't support all alert types. As a result, this security alert, which is based on Kubernetes audit events, is not supported for GKE clusters.
 
 <sup><a name="footnote3"></a>3</sup>: This alert is supported on Windows nodes/containers.