Merge pull request #301674 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/azure-functions/functions-reference-python.md

@@ -842,7 +842,7 @@ The *host.json* file must also be updated to include an HTTP `routePrefix`, as s
   "extensionBundle": 
   {
     "id": "Microsoft.Azure.Functions.ExtensionBundle",
-    "version": "[3.*, 4.0.0)"
+    "version": "[4.*, 5.0.0)"
   },
   "extensions": 
   {
@@ -910,7 +910,7 @@ You can use Asynchronous Server Gateway Interface (ASGI)-compatible and Web Serv
   "extensionBundle": 
   {
     "id": "Microsoft.Azure.Functions.ExtensionBundle",
-    "version": "[2.*, 3.0.0)"
+    "version": "[4.*, 5.0.0)"
   },
   "extensions": 
   {

articles/iot-operations/deploy-iot-ops/overview-deploy.md

@@ -29,6 +29,9 @@ To install Azure IoT Operations, have the following hardware requirements availa
 | Available memory for Azure IoT Operations (RAM) | 10-GB | Depends on usage |
 | CPU  | 4 vCPUs | 8 vCPUs     |
 
+>[!NOTE]
+>The minimum configuration is appropriate when running AIO only.
+
 ## Choose your features
 
 Azure IoT Operations offers two deployment modes. You can choose to deploy with *test settings*, a basic subset of features that are simpler to get started with for evaluation scenarios. Or, you can choose to deploy with *secure settings*, the full feature set.

articles/role-based-access-control/permissions/hybrid-multicloud.md

@@ -228,7 +228,7 @@ Azure service: [Azure Arc](/azure/azure-arc/)
 > | Microsoft.HybridCompute/machines/UpgradeExtensions/action | Upgrades Extensions on Azure Arc machines |
 > | Microsoft.HybridCompute/machines/assessPatches/action | Assesses any Azure Arc machines to get missing software patches |
 > | Microsoft.HybridCompute/machines/installPatches/action | Installs patches on any Azure Arc machines |
-> | Microsoft.HybridCompute/machines/listAccessDetails/action | Retreives the access details for a machines resource |
+> | Microsoft.HybridCompute/machines/listAccessDetails/action | Retrieves the access details for a machines resource |
 > | Microsoft.HybridCompute/machines/addExtensions/action | Setup Extensions on Azure Arc machines |
 > | Microsoft.HybridCompute/machines/extensions/read | Reads any Azure Arc extensions |
 > | Microsoft.HybridCompute/machines/extensions/write | Installs or Updates an Azure Arc extensions |

articles/sentinel/sap/deploy-data-connector-agent-container.md

@@ -348,7 +348,7 @@ At this stage, the system's **Health** status is **Pending**. If the agent is up
     - If you have the **Entra ID Application Developer** role or higher, continue to the next step.
     - If you don't have the **Entra ID Application Developer** role or higher:
         - Share the DCR ID with your Entra ID administrator or colleague with the required permissions. 
-        - Ensure that the **Monitoring Metrics Publishing** role is assigned on the DCR, with the service principal assignment, using the client ID from the Entra ID app registration.                      
+        - Ensure that the **Monitoring Metrics Publisher** role is assigned on the DCR, with the service principal assignment, using the client ID from the Entra ID app registration.                      
         - Retrieve the client ID and client secret from the Entra ID app registration to use for authorization on the DCR. 
         
         The SAP admin uses the client ID and client secret information to post to the DCR.              

articles/storage/common/redundancy-migration.md

@@ -350,7 +350,7 @@ Some storage account features aren't compatible with other features or operation
 
 Boot diagnostics doesn't support premium storage accounts or zone-redundant storage accounts. When either premium or zone-redundant storage accounts are used for boot diagnostics, users receive a `StorageAccountTypeNotSupported` error upon starting their virtual machine (VM). 
 
-Any conversion attempts to add zonal redundancy, such as LRS to ZRS or GRS to GZRS, will fail. To convert your account to a zone-redundant SKU, disable boot diagnostics on your account and resubmit the request. To learn more about boot diagnostics, review the [Azure boot diagnotics](/azure/virtual-machines/boot-diagnostics#enable-managed-boot-diagnostics) article.
+Any conversion attempts to add zonal redundancy, such as LRS to ZRS or GRS to GZRS, will fail. To convert your account to a zone-redundant SKU, disable boot diagnostics on your account and resubmit the request. To learn more about boot diagnostics, review the [Azure boot diagnostics](/azure/virtual-machines/boot-diagnostics#enable-managed-boot-diagnostics) article.
 
 ### Storage account type
 

articles/storage/files/files-redundancy.md

@@ -213,7 +213,7 @@ $token = Get-AzAccessToken
 # Invoke SRP list SKU API, and get the returned SKU list
 $result = Invoke-RestMethod -Method Get -Uri "https://management.azure.com/subscriptions/$($subscriptionID)/providers/Microsoft.Storage/skus?api-version=2024-01-01" -Headers @{"Authorization" = "Bearer $($token.Token)"}
 
-# Filter the SKU list to get the required information, customization requried here to get the best result.
+# Filter the SKU list to get the required information, customization required here to get the best result.
 $filteredResult = $result | `
     Select-Object -ExpandProperty value | `
     Where-Object {

articles/storage/files/storage-files-configure-p2s-vpn-linux.md

@@ -227,7 +227,7 @@ sudo ipsec up $VIRTUAL_NETWORK_NAME
 
 ## Mount Azure file share
 
-After seting up your Point-to-Site VPN, you can mount your Azure file share. See [Mount SMB file shares to Linux](storage-how-to-use-files-linux.md) or [Mount NFS file share to Linux](storage-files-how-to-mount-nfs-shares.md). 
+After setting up your Point-to-Site VPN, you can mount your Azure file share. See [Mount SMB file shares to Linux](storage-how-to-use-files-linux.md) or [Mount NFS file share to Linux](storage-files-how-to-mount-nfs-shares.md). 
 
 ## See also
 

articles/storage/solution-integration/validated-partners/data-management/komprise-quick-start-guide.md

@@ -57,7 +57,7 @@ With a quick install of a local Komprise data Observer, in 30 minutes or less yo
     - Date set too large for destination storage service in file count or capacity
     - Data sets with an exceedingly large number of tiny files or with a large number of empty directories
     - Slow-performing shares
-    - Lack of destination support for sparce files or symbolic links
+    - Lack of destination support for sparse files or symbolic links
 
 Komprise knows it can be challenging to find just the right data across billions of files. Komprise Deep Analytics builds a Global File Index of all your file’s metadata, giving a unified way to search, tag and create select data sets across storage silos. You can identify orphan data, data by name, location, owner, date, application type or extension. Administrators can use these queries and tagged data sets to move, copy, confine, or feed your data pipelines. They can also set data workflow policies.  This allows business to use other Azure cloud data services like personal data identification, running cloud data analytics, and culling and feeding edge data to cloud data lakes.