Merge pull request #252516 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: TimShererWithAquent

articles/active-directory/develop/custom-extension-get-started.md

@@ -408,7 +408,7 @@ The following JSON snippet demonstrates how to configure these properties.
 
 ## Step 4: Assign a custom claims provider to your app
 
-For tokens to be issued with claims incoming from the custom authentication extension, you must assign a custom claims provider to your application. This is based on the token audience, so the provider must be assgined to the client application to receive claims in an ID token, and to the resource application to receive claims in an access token. The custom claims provider relies on the custom authentication extension configured with the **token issuance start** event listener. You can choose whether all, or a subset of claims, from the custom claims provider are mapped into the token.
+For tokens to be issued with claims incoming from the custom authentication extension, you must assign a custom claims provider to your application. This is based on the token audience, so the provider must be assigned to the client application to receive claims in an ID token, and to the resource application to receive claims in an access token. The custom claims provider relies on the custom authentication extension configured with the **token issuance start** event listener. You can choose whether all, or a subset of claims, from the custom claims provider are mapped into the token.
 
 Follow these steps to connect the *My Test application* with your custom authentication extension:
 

articles/active-directory/hybrid/cloud-sync/reference-powershell.md

@@ -142,6 +142,21 @@ This cmdlet modifies *AADConnectProvisioningAgent.exe.config* to disable verbose
 
 This cmdlet pauses synchronization.
 
+### Disable-AADCloudSyncToolsDirSyncAccidentalDeletionPrevention
+
+Disables accidentalDeletionPrevention tenant feature
+``` powershell
+Disable-AADCloudSyncToolsDirSyncAccidentalDeletionPrevention -tenantId <TenantId>
+```
+
+This cmdlet requires `TenantId` of the Azure AD tenant. It will verify if Accidental Deletion Prevention feature, set on the tenant with Azure AD Connect (ADSync, not Cloud Sync), is enabled and disables it.
+
+#### Example:
+``` powershell
+Disable-AADCloudSyncToolsDirSyncAccidentalDeletionPrevention -tenantId "340ab039-1234-5678-9012-28fe88f83980"
+```
+
+
 ## Next steps 
 
 - [What is provisioning?](../what-is-provisioning.md)

articles/azure-functions/functions-host-json-v1.md

@@ -294,7 +294,7 @@ Configuration setting for the [SendGrind output binding](functions-bindings-send
 Configuration setting for [Service Bus triggers and bindings](functions-bindings-service-bus.md).
 
 ```json
-{
+{ "extensions":
     "serviceBus": {
       "maxConcurrentCalls": 16,
       "prefetchCount": 100,

articles/azure-resource-manager/management/async-operations.md

@@ -36,7 +36,7 @@ There are two different ways to monitor the status the asynchronous operation. Y
 
 If `Azure-AsyncOperation` isn't one of the header values, then look for:
 
-* `Location` - URL for determining when an operation has completed. Only use this value only when `Azure-AsyncOperation` isn't returned.
+* `Location` - URL for determining when an operation has completed. Use this value only when `Azure-AsyncOperation` isn't returned.
 * `Retry-After` - The number of seconds to wait before checking the status of the asynchronous operation.
 
 > [!NOTE]
@@ -205,4 +205,4 @@ If the request is still running, you receive a status code 202. If the request h
 ## Next steps
 
 * For documentation about each REST operation, see [REST API documentation](/rest/api/azure/).
-* For information about deploying templates through the Resource Manager REST API, see [Deploy resources with Resource Manager templates and Resource Manager REST API](../templates/deploy-rest.md).
+* For information about deploying templates through the Resource Manager REST API, see [Deploy resources with Resource Manager templates and Resource Manager REST API](../templates/deploy-rest.md).

articles/batch/batch-docker-container-workloads.md

@@ -72,6 +72,31 @@ For Linux container workloads, Batch currently supports the following Linux imag
   - Offer: `centos-container-rdma`
   - Offer: `ubuntu-server-container-rdma`
 
+- Publisher: `microsoft-dsvm`
+  - Offer: `ubuntu-hpc`
+
+#### Notes
+  The docker data root of the above images lies in different places:
+  - For the batch image `microsoft-azure-batch` (Offer: `centos-container-rdma`, etc), the docker data root is mapped to `/mnt/batch/docker`, which is usually located on the temporary disk.
+  - For the HPC image, or `microsoft-dsvm` (Offer: `ubuntu-hpc`, etc), the docker data root is unchanged from the Docker default which is `/var/lib/docker` on Linux and `C:\ProgramData\Docker` on Windows. These folders are usually located on the OS disk.
+
+    When using non-Batch images, the OS disk has the potential risk of being filled up quickly as container images are downloaded.
+#### Potential solutions for customer
+
+Change the docker data root in a start task when creating a pool in BatchExplorer. Here's an example of the Start Task command:
+```csharp
+1)  sudo systemctl stop docker
+2)  sudo vi /lib/systemd/system/docker.service
+    +++
+    FROM:
+    ExecStart=/usr/bin/docker daemon -H fd://
+    TO:
+    ExecStart=/usr/bin/docker daemon -g /new/path/docker -H fd://
+    +++
+3)  sudo systemctl daemon-reload
+4)  sudo systemctl start docker
+```
+
 These images are only supported for use in Azure Batch pools and are geared for Docker container execution. They feature:
 
 - A pre-installed Docker-compatible [Moby container runtime](https://github.com/moby/moby).

articles/machine-learning/how-to-debug-pipeline-reuse-issues.md

@@ -36,7 +36,7 @@ Azure Machine Learning pipeline has holistic logic to calculate whether a compon
 
 Reuse criteria:
 
-- Component definition `is_determinstic` = true
+- Component definition `is_deterministic` = true
 - Pipeline runtime setting `ForceReRun` = false
 - Component code, environment definition, inputs and parameters, output settings, and run settings are all the same.
 

articles/machine-learning/prompt-flow/how-to-end-to-end-llmops-with-prompt-flow.md

@@ -151,7 +151,7 @@ Go to workspace portal, select **Prompt flow** -> **Runtime** -> **Add**, then f
 Clone repo to your local machine.
 
 ```bash
-    git clone https://github.com/<user-name>/llmops-pipeline
+    git clone https://github.com/<user-name>/llmops-gha-demo
  ```
 
 ### Update workflow to connect to your Azure Machine Learning workspace

articles/search/tutorial-optimize-indexing-push-api.md

@@ -39,7 +39,7 @@ The following services and tools are required for this tutorial.
 
 ## Download files
 
-Source code for this tutorial is in the [optimzize-data-indexing/v11](https://github.com/Azure-Samples/azure-search-dotnet-scale/tree/main/optimize-data-indexing/v11) folder in the [Azure-Samples/azure-search-dotnet-samples](https://github.com/Azure-Samples/azure-search-dotnet-samples) GitHub repository.
+Source code for this tutorial is in the [optimize-data-indexing/v11](https://github.com/Azure-Samples/azure-search-dotnet-scale/tree/main/optimize-data-indexing/v11) folder in the [Azure-Samples/azure-search-dotnet-samples](https://github.com/Azure-Samples/azure-search-dotnet-samples) GitHub repository.
 
 ## Key considerations
 

articles/service-bus-messaging/message-deferral.md

@@ -37,3 +37,7 @@ Try the samples in the language of your choice to explore Azure Service Bus feat
 See samples for the older .NET and Java client libraries here:
 - [Azure Service Bus client library samples for .NET (legacy)](https://github.com/Azure/azure-service-bus/tree/master/samples/DotNet/Microsoft.Azure.ServiceBus/) - See the **Deferral** sample. 
 - [Azure Service Bus client library samples for Java (legacy)](https://github.com/Azure/azure-service-bus/tree/master/samples/Java/azure-servicebus/MessageBrowse)
+
+## Related resources
+
+- [Tutorial showing the use of message deferral as a part of a workflow, using NServiceBus](https://docs.particular.net/tutorials/nservicebus-sagas/2-timeouts/)

articles/spring-apps/how-to-configure-health-probes-graceful-termination.md

@@ -198,7 +198,7 @@ Use the following steps to customize your application using Azure CLI.
 
 ## Best practices
 
-Use the following best practices when adding your own persistent storage to Azure Spring Apps:
+Use the following best practices when adding health probes to Azure Spring Apps:
 
 - Use liveness and readiness probes together. Azure Spring Apps provides two approaches for service discovery at the same time. When the readiness probe fails, the app instance is removed only from Kubernetes service discovery. A properly configured liveness probe can remove the issued app instance from Eureka service discovery to avoid unexpected cases. For more information about service discovery, see [Discover and register your Spring Boot applications](how-to-service-registration.md).