Merge pull request #262664 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: rmca14

articles/aks/access-control-managed-azure-ad.md

@@ -8,10 +8,10 @@ ms.custom: devx-track-azurecli
 
 # Cluster access control with AKS-managed Microsoft Entra integration
 
-When you integrate Microsoft Entra ID with your AKS cluster, you can use [Conditional Access][aad-conditional-access] or Privileged Identity Management (PIM) for just-in-time requests to control access to your cluster. This article shows you how to enable Conditional Access and PIM on your AKS clusters.
+When you integrate Microsoft Entra ID with your AKS cluster, you can use [Conditional Access][aad-conditional-access] or [Privileged Identity Management (PIM)][pim-configure] for just-in-time requests to control access to your cluster. This article shows you how to enable Conditional Access and PIM on your AKS clusters.
 
 > [!NOTE]
-> Microsoft Entra Conditional Access and Privileged Identity Management are Microsoft Entra ID P1 or P2 capabilities requiring a Premium P2 SKU. For more on Microsoft Entra ID SKUs, see the [pricing guide][aad-pricing].
+> Microsoft Entra Conditional Access and Privileged Identity Management (PIM) are Microsoft Entra ID P1, P2 or Governance capabilities requiring a Premium P2 SKU. For more on Microsoft Entra ID licenses and SKUs, see [Microsoft Entra ID Governance licensing fundamentals][licensing-fundamentals] and [pricing guide][aad-pricing].
 
 ## Before you begin
 
@@ -169,6 +169,8 @@ Make sure the admin of the security group has given your account an *Active* ass
 
 <!-- LINKS - Internal -->
 [aad-conditional-access]: ../active-directory/conditional-access/overview.md
+[pim-configure]: /entra/id-governance/privileged-identity-management/pim-configure
+[licensing-fundamentals]: /entra/id-governance/licensing-fundamentals
 [az-aks-get-credentials]: /cli/azure/aks#az_aks_get_credentials
 [az-role-assignment-create]: /cli/azure/role/assignment#az_role_assignment_create
 [aad-assignments]: ../active-directory/privileged-identity-management/groups-assign-member-owner.md#assign-an-owner-or-member-of-a-group

articles/aks/azure-ad-rbac.md

@@ -134,7 +134,7 @@ AKSDEV_ID=$(az ad user create \
   --display-name "AKS Dev" \
   --user-principal-name $AAD_DEV_UPN \
   --password $AAD_DEV_PW \
-  --query objectId -o tsv)
+  --query id -o tsv)
 ```
 
 2. Add the user to the *appdev* group created in the previous section using the [`az ad group member add`][az-ad-group-member-add] command.
@@ -163,7 +163,7 @@ AKSSRE_ID=$(az ad user create \
   --display-name "AKS SRE" \
   --user-principal-name $AAD_SRE_UPN \
   --password $AAD_SRE_PW \
-  --query objectId -o tsv)
+  --query id -o tsv)
 
 # Add the user to the opssre Azure AD group
 az ad group member add --group opssre --member-id $AKSSRE_ID

articles/aks/azure-csi-files-storage-provision.md

@@ -150,7 +150,7 @@ A persistent volume claim (PVC) uses the storage class object to dynamically pro
 
     ```output
     NAME           STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
-    my-azurefile   Bound     pvc-8436e62e-a0d9-11e5-8521-5a8664dc0477   10Gi       RWX            my-azurefile      5m
+    my-azurefile   Bound     pvc-8436e62e-a0d9-11e5-8521-5a8664dc0477   100Gi       RWX            my-azurefile      5m
     ```
 
 ### Use the persistent volume

articles/aks/planned-maintenance.md

@@ -14,7 +14,7 @@ author: nickomang
 
 Your AKS cluster has regular maintenance performed on it automatically. There are two types of regular maintenance - AKS initiated and those that you initiate. Planned Maintenance feature allows you to run both types of maintenance in a cadence of your choice thereby minimizing any workload impact. 
 
-AKS intiated maintenance refers to the AKS releases. These releases are weekly rounds of fixes and feature and component updates that affect your clusters. The type of maintenance that you initiate regularly are [cluster auto-upgrades][aks-upgrade] and [Node OS automatic security updates][node-image-auto-upgrade].
+AKS initiated maintenance refers to the AKS releases. These releases are weekly rounds of fixes and feature and component updates that affect your clusters. The type of maintenance that you initiate regularly are [cluster auto-upgrades][aks-upgrade] and [Node OS automatic security updates][node-image-auto-upgrade].
 
 There are currently three available configuration types: `default`, `aksManagedAutoUpgradeSchedule`, `aksManagedNodeOSUpgradeSchedule`:
 

articles/azure-functions/durable/durable-functions-orchestrations.md

@@ -431,7 +431,7 @@ public static async Task<object> RunOrchestrator(
 
 [FunctionName("CourseRecommendations")]
 public static async Task<object> Mapper(
-    [ActivityTrigger] (string Major, int UniversityYear) inputs, FunctionContext executionContext)
+    [ActivityTrigger] (string Major, int UniversityYear) studentInfo, FunctionContext executionContext)
 {
     // retrieve and return course recommendations by major and university year
     return new

articles/azure-functions/functions-reference.md

@@ -316,7 +316,7 @@ To use an identity-based connection for `AzureWebJobsStorage`, configure the fol
 
 [Common properties for identity-based connections](#common-properties-for-identity-based-connections) may also be set as well.
 
-If you're configuring `AzureWebJobsStorage` using a storage account that uses the default DNS suffix and service name for global Azure, following the `https://<accountName>.blob/queue/file/table.core.windows.net` format, you can instead set `AzureWebJobsStorage__accountName` to the name of your storage account. The endpoints for each storage service are inferred for this account. This doesn't work when the storage account is in a sovereign cloud or has a custom DNS.
+If you're configuring `AzureWebJobsStorage` using a storage account that uses the default DNS suffix and service name for global Azure, following the `https://<accountName>.[blob|queue|file|table].core.windows.net` format, you can instead set `AzureWebJobsStorage__accountName` to the name of your storage account. The endpoints for each storage service are inferred for this account. This doesn't work when the storage account is in a sovereign cloud or has a custom DNS.
 
 | Setting                       | Description                                | Example value                                        |
 |-----------------------------------------------------|--------------------------------------------|------------------------------------------------|

articles/container-registry/container-registry-troubleshoot-access.md

@@ -65,7 +65,7 @@ Related links:
 
 * [Configure rules to access an Azure container registry behind a firewall](container-registry-firewall-access-rules.md)
 * [HTTP/HTTPS proxy configuration](https://docs.docker.com/config/daemon/systemd/#httphttps-proxy)
-* [Geo-replicationin Azure Container Registry](container-registry-geo-replication.md)
+* [Geo-replication in Azure Container Registry](container-registry-geo-replication.md)
 * [Monitor Azure Container Registry](monitor-service.md)
 
 ### Configure public access to registry

articles/cosmos-db/nosql/quickstart-dotnet.md

@@ -310,15 +310,15 @@ The code to access database resources is in the `GenerateQueryDataAsync` method
 
 Use the <xref:Microsoft.Azure.Cosmos.CosmosClient.GetDatabase%2A> method to return a reference to the specified database.
 
-:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Pages/Index.razor" id="get_database":::
+:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Services/CosmosDbService.cs" id="get_database":::
 
 ### Get a container
 
 The code to access container resources is also in the `GenerateQueryDataAsync` method.
 
 The <xref:Microsoft.Azure.Cosmos.Database.GetContainer%2A> returns a reference to the specified container.
 
-:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Pages/Index.razor" id="get_container":::
+:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Services/CosmosDbService.cs" id="get_container":::
 
 ### Create an item
 
@@ -328,24 +328,24 @@ The easiest way to create a new item in a container is to first build a C# class
 
 In the `GenerateQueryDataAsync` method, create an item in the container by calling <xref:Microsoft.Azure.Cosmos.Container.UpsertItemAsync%2A>.
 
-:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Pages/Index.razor" id="create_item":::
+:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Services/CosmosDbService.cs" id="create_item":::
 
 ### Read an item
 
 In Azure Cosmos DB, you can perform a point read operation by using both the unique identifier (`id`) and partition key fields. In the SDK, call <xref:Microsoft.Azure.Cosmos.Container.ReadItemAsync%2A> passing in both values to return a deserialized instance of your C# type.
 Still in the `GenerateQueryDataAsync` method, use `ReadItemAsync<Product>` to serialize the item using the `Product` type.
 
-:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Pages/Index.razor" id="read_item":::
+:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Services/CosmosDbService.cs" id="read_item":::
 
 ### Query items
 
 After you insert an item, you can run a query to get all items that match a specific filter. This example runs the SQL query: `SELECT * FROM products p WHERE p.category = "gear-surf-surfboards"`. This example uses the QueryDefinition type and a parameterized query expression for the partition key filter. Once the query is defined, call <xref:Microsoft.Azure.Cosmos.Container.GetItemQueryIterator%2A> to get a result iterator that manages the pages of results. In the example, the query logic is also in the `GenerateQueryDataAsync` method.
 
-:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Pages/Index.razor" id="query_items":::
+:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Services/CosmosDbService.cs" id="query_items":::
 
 Then, use a combination of `while` and `foreach` loops to retrieve pages of results and then iterate over the individual items.
 
-:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Pages/Index.razor" id="parse_results":::
+:::code language="csharp" source="~/cosmos-db-nosql-dotnet-quickstart/src/web/Services/CosmosDbService.cs" id="parse_results":::
 
 ## Clean up resources
 

articles/dms/pre-reqs.md

@@ -87,7 +87,7 @@ Azure Database Migration Service prerequisites that are common across all suppor
     > Set-AzRoleDefinition -Role $aRole
     > }
     >
-    > function Update-DmsConributorRole() {
+    > function Update-DmsContributorRole() {
     > $aRole = Get-AzRoleDefinition "Azure Database Migration Contributor"
     > $aRole.Actions = $writerActions
     > $aRole.NotActions = @()
@@ -98,7 +98,7 @@ Azure Database Migration Service prerequisites that are common across all suppor
     > New-DmsReaderRole
     > New-DmsContributorRole
     > Update-DmsReaderRole
-    > Update-DmsConributorRole
+    > Update-DmsContributorRole
     > ```
 
 ## Prerequisites for migrating SQL Server to Azure SQL Database

articles/site-recovery/vmware-azure-tutorial-prepare-on-premises.md

@@ -50,7 +50,7 @@ Create the account as follows:
 **Task** | **Role/Permissions** | **Details**
 --- | --- | ---
 **VM discovery** | At least a read-only user<br/><br/> Data Center object –> Propagate to Child Object, role=Read-only | User assigned at datacenter level, and has access to all the objects in the datacenter.<br/><br/> To restrict access, assign the **No access** role with the **Propagate to child** object, to the child objects (vSphere hosts, datastores, VMs and networks).
-**Full replication, failover, failback** |  Create a role (Azure_Site_Recovery) with the required permissions, and then assign the role to a VMware user or group<br/><br/> Data Center object –> Propagate to Child Object, role=Azure_Site_Recovery<br/><br/> Datastore -> Allocate space, browse datastore, low-level file operations, remove file, update virtual machine files<br/><br/> Network -> Network assign<br/><br/> Resource -> Assign VM to resource pool, migrate powered off VM, migrate powered on VM<br/><br/> Tasks -> Create task, update task<br/><br/> Virtual machine -> Configuration<br/><br/> Virtual machine -> Interact -> answer question, device connection, configure CD media, configure floppy media, power off, power on, VMware tools install<br/><br/> Virtual machine -> Inventory -> Create, register, unregister<br/><br/> Virtual machine -> Provisioning -> Allow virtual machine download, allow virtual machine files upload<br/><br/> Virtual machine -> Snapshots -> Remove snapshots | User assigned at datacenter level, and has access to all the objects in the datacenter.<br/><br/> To restrict access, assign the **No access** role with the **Propagate to child** object, to the child objects (vSphere hosts, datastores, VMs and networks).
+**Full replication, failover, failback** |  Create a role (Azure_Site_Recovery) with the required permissions, and then assign the role to a VMware user or group<br/><br/> Data Center object –> Propagate to Child Object, role=Azure_Site_Recovery<br/><br/> Datastore -> Allocate space, browse datastore, low-level file operations, remove file, update virtual machine files<br/><br/> Network -> Network assign<br/><br/> Resource -> Assign VM to resource pool, migrate powered off VM, migrate powered on VM<br/><br/> Tasks -> Create task, update task<br/><br/> Virtual machine -> Configuration<br/><br/> Virtual machine -> Interact -> answer question, device connection, configure CD media, configure floppy media, power off, power on, VMware tools install<br/><br/> Virtual machine -> Inventory -> Create, register, unregister<br/><br/> Virtual machine -> Provisioning -> Allow virtual machine download, allow virtual machine files upload<br/><br/> Virtual machine -> Snapshots -> Remove snapshots, Create snapshots | User assigned at datacenter level, and has access to all the objects in the datacenter.<br/><br/> To restrict access, assign the **No access** role with the **Propagate to child** object, to the child objects (vSphere hosts, datastores, VMs and networks).
 
 ## Prepare an account for Mobility service installation