Merge pull request #301961 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: Taojunshen

articles/automation/shared-resources/certificates.md

@@ -56,7 +56,9 @@ Use the function in the following table to access certificates in a Python 2 and
 
 ## Create a new certificate
 
-When you create a new certificate, you upload a .cer or .pfx file to Automation. If you mark the certificate as exportable, then you can transfer it out of the Automation certificate store. If it isn't exportable, then it can only be used for signing within the runbook or DSC configuration. Automation requires the certificate to have the provider **Microsoft Enhanced RSA and AES Cryptographic Provider**.
+When you create a new certificate, you upload a .cer or .pfx file to Automation. If you mark the certificate as exportable, then you can transfer it out of the Automation certificate store. If it isn't exportable, then it can only be used for signing within the runbook or DSC configuration. 
+> [!NOTE]
+> Azure Automation requires the certificate to have the provider **Microsoft Enhanced RSA and AES Cryptographic Provider**.
 
 ### Create a new certificate with the Azure portal
 

articles/automation/shared-resources/modules.md

@@ -96,7 +96,12 @@ The default modules are also known as global modules. In the Azure portal, the *
 
 ## Internal cmdlets
 
-Azure Automation supports internal cmdlets that are only available when you execute runbooks in the Azure sandbox environment or on a Windows Hybrid Runbook Worker. The internal module `Orchestrator.AssetManagement.Cmdlets` is installed by default in your Automation account and when the Windows Hybrid Runbook Worker role is installed on the machine. 
+Azure Automation provides internal cmdlets that are exclusively available when runbooks are executed in the Azure sandbox environment or on a Windows Hybrid Runbook Worker. The `Orchestrator.AssetManagement.Cmdlets` module, containing these internal cmdlets, is installed by default in your Automation account and specifically when the Windows Hybrid Runbook Worker role is installed on a Windows machine.
+
+> [!NOTE]
+> This functionality is not available on Linux Hybrid Runbook Workers.
+
+
 
 The following table defines the internal cmdlets. These cmdlets are designed to be used instead of Azure PowerShell cmdlets to interact with your Automation account resources. They can retrieve secrets from encrypted variables, credentials, and encrypted connections.
 

articles/azure-app-configuration/rest-api-key-value.md

@@ -412,7 +412,7 @@ Content-Type: application/problem+json; charset="utf-8"
 ```json
 {
     "type": "https://azconfig.io/errors/key-locked",
-    "title": "Modifing key '{key}' is not allowed",
+    "title": "Modifying key '{key}' is not allowed",
     "name": "{key}",
     "detail": "The key is read-only. To allow modification unlock it first.",
     "status": 409

articles/azure-functions/functions-bindings-mongodb-vcore.md

@@ -24,7 +24,7 @@ Using the Azure Cosmos DB for MongoDB (vCore) extension, you can build functions
 | Query the database | [Azure Cosmos DB for MongoDB (vCore) input binding](functions-bindings-mongodb-vcore-input.md) |
 
 Considerations for the Azure Cosmos DB for MongoDB (vCore) extension:
-+ Only [C# apps that run in-proces with the host](./functions-dotnet-class-library.md) are currently supported in preview.
++ Only [C# apps that run in-process with the host](./functions-dotnet-class-library.md) are currently supported in preview.
 + The Azure Cosmos DB for MongoDB (vCore) binding extension doesn't currently support Microsoft Entra authentication and managed identities. 
 + Your app must be using version 4.x of the Azure Functions runtime.
 

articles/backup/backup-azure-monitoring-alerts.md

@@ -44,7 +44,7 @@ The following table lists the differences between classic backup alerts and buil
 | Actions | Classic alerts | Built-in Azure Monitor alerts |
 | --- | --- | --- |
 | **Setting up notifications** | - You must enable the configure notifications feature for each Recovery Services vault, along with the email id(s) to which the notifications should be sent. <br><br> - For certain destructive operations, email notifications are sent to the subscription owner, admin and co-admin irrespective of the notification settings of the vault.| - Notifications are configured by creating an alert processing rule. <br><br> - While *alerts* are generated by default and can't be turned off for destructive operations, the notifications are in the control of the user, allowing you to clearly specify which set of email address (or other notification endpoints) you wish to route alerts to. |
-| **Notification suppression for database backup scenarios** | When there are multiple failures for the same database due to the same error code, a single alert is generated (with the occurrence count updated for each failure type) and a new alert is only generated when the original alert is inactivated. | The behavior is currently different. Here, a separate alert is generated for every backup failure. If there's a window of time when backups will fail for a certain known item (for example, during a maintenance window), you can create a suppression rule to suppress email noise for that backup item during the given period. |
+| **Notification suppression for database backup scenarios** | When there are multiple failures for the same database due to the same error code, a single alert is generated (with the occurrence count updated for each failure type) and a new alert is only generated when the original alert is deactivated. | The behavior is currently different. Here, a separate alert is generated for every backup failure. If there's a window of time when backups will fail for a certain known item (for example, during a maintenance window), you can create a suppression rule to suppress email noise for that backup item during the given period. |
 | **Pricing** | There are no additional charges for this solution. | Alerts for critical operations/failures generate by default (that you can view in the Azure portal or via non-portal interfaces) at no additional charge. However, to route these alerts to a notification channel (such as email), it incurs a minor charge for notifications beyond the *free tier* (of 1000 emails per month). Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/). |
 
 > [!NOTE]

articles/backup/move-to-azure-monitor-alerts.md

@@ -52,7 +52,7 @@ The following are alerts from Azure Backup solutions are:
 
 For Azure workload backup solutions, such as SQL and SAP HANA, log backups can be generated frequently (up to every 15 minutes according to the policy). So, you might encounter frequent log backup failures (up to every 15 minutes). In this scenario, the end user will be overwhelmed if an alert is raised for each failure occurrence.
 
-So, an alert is sent for the first occurrence, and if the later failures are because of the same root cause, then further alerts aren't generated. The first alert is updated with the failure count. But if you've inactivated the alert, the next occurrence will trigger another alert and this will be treated as the first alert for that occurrence. This is how Azure Backup performs alert consolidation for SQL and SAP HANA backups.
+So, an alert is sent for the first occurrence, and if the later failures are because of the same root cause, then further alerts aren't generated. The first alert is updated with the failure count. But if you've deactivated the alert, the next occurrence will trigger another alert and this will be treated as the first alert for that occurrence. This is how Azure Backup performs alert consolidation for SQL and SAP HANA backups.
 
 On-demand backup jobs aren't consolidated.
 
@@ -94,9 +94,9 @@ If the frequency was set to an hourly digest, and an alert was raised and resolv
 
 ## Inactivating alerts
 
-To inactivate/resolve an active alert, you can select the list item corresponding to the alert you wish to inactivate. This opens up a screen that shows detailed information about the alert, with an **Inactivate** button at the top. Selecting this button will change the status of the alert to **Inactive**. You may also inactivate an alert by right-clicking the list item corresponding to that alert and selecting **Inactivate**.
+To deactivate/resolve an active alert, you can select the list item corresponding to the alert you wish to deactivate. This opens up a screen that shows detailed information about the alert, with an **Inactivate** button at the top. Selecting this button will change the status of the alert to **Inactive**. You may also deactivate an alert by right-clicking the list item corresponding to that alert and selecting **Inactivate**.
 
-:::image type="content" source="./media/backup-azure-monitoring-laworkspace/vault-alert-inactivate.png" alt-text="Screenshot showing how to inactivate alerts via Backup center.":::
+:::image type="content" source="./media/backup-azure-monitoring-laworkspace/vault-alert-inactivate.png" alt-text="Screenshot showing how to deactivate alerts via Backup center.":::
 
 
 

articles/communication-services/concepts/interop/enable-closed-captions.md

@@ -27,7 +27,7 @@ In this document, we're going to be looking at specifically Teams interoperabili
 | Enable captions in Teams meeting | ✔︎ | ✔︎ | ✔︎ | 
 | Enable captions in Teams call | ✔︎ | ✔︎ | ✔︎ | 
 
-*✕ = not supprted in current release.*
+*✕ = not supported in current release.*
 
 ### Translated Captions
 

articles/communication-services/samples/integrate-azure-communication-services-with-copilot-studio.md

@@ -134,7 +134,7 @@ app.MapPost("/api/incomingCall", async (
         }
         catch (Exception ex)
         {
-            logger.LogError($"Answer call exeception : {ex.StackTrace}");
+            logger.LogError($"Answer call exception : {ex.StackTrace}");
         }
     }
     return Results.Ok();

articles/databox-online/azure-stack-edge-gpu-troubleshoot-activation.md

@@ -40,7 +40,7 @@ The following table summarizes the errors related to device activation and the c
 | Error   message| Recommended   resolution |
 |------------------------------------------------------|--------------------------------------|
 | If the Channel Integrity Key in the Azure Key Vault was deleted, and you try to perform any operations that involve encryption - for example, **Add User**, **Add Share**, or **Configure Compute** - then you will receive this error.  |If the Channel Integrity Key in the key vault was deleted, but the key is still within the purge duration, follow the steps in [Undo Key vault key removal](/powershell/module/az.keyvault/undo-azkeyvaultkeyremoval). <br>If the purge protection duration has elapsed, and if you've backed up the key, you can restore the key from the backup. Otherwise, you can't recover the key. Contact Microsoft Support for next steps. |
-<!--|Remove this after checking with Noopur - customer doesnt need to do anything - If the Channel Integrity Key in the Azure Key Vault was deleted before the activation of the device, and the activation key is regenerated, you'll receive this error. <br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png) | The Channel Integrity Key will be recreated, and the metadata is updated.
+<!--|Remove this after checking with Noopur - customer doesn't need to do anything - If the Channel Integrity Key in the Azure Key Vault was deleted before the activation of the device, and the activation key is regenerated, you'll receive this error. <br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png) | The Channel Integrity Key will be recreated, and the metadata is updated.
 |-->
 
 ## Audit logging errors

articles/defender-for-iot/organizations/api/sensor-inventory-apis.md

@@ -609,7 +609,7 @@ This section lists the supported values for the [type](#type) response field.
 - `Backup Server`
 - `Meter`
 - `Barcode Scanner`
-- `Uninterruptable Power Supply`
+- `Uninterruptible Power Supply`
    :::column-end:::
    :::column span="":::
 - `Variable Frequency Drive`