Merge pull request #239026 from MicrosoftDocs/repo_sync_working_branch

Resolve syncing conflicts from repo_sync_working_branch to main

Author: huypub

articles/active-directory/fundamentals/customize-branding.md

@@ -40,7 +40,12 @@ The **Global Administrator** role is required to customize company branding.
 
 ## Before you begin
 
-You can customize the sign-in experience when users sign in to your organization's tenant-specific apps, such as `https://outlook.com/woodgrove.com`, or when passing a domain variable, such as `https://passwordreset.microsoftonline.com/?whr=woodgrove.com`.
+You can customize the sign-in experience when users sign in to your organization by passing a domain variable:
+Microsoft 365 Portal: `https://login.microsoftonline.com/?whr=contoso.com`
+Outlook: `https://outlook.com/contoso.com`
+Teams: `https://teams.microsoft.com/?tenantId=contoso.com`
+MyApps: `http://myapps.microsoft.com/?whr=contoso.com`
+Azure AD Self-service Password Reset: `https://passwordreset.microsoftonline.com/?whr=contoso.com`
 
 Custom branding appears after users sign in. Users that start the sign-in process at a site like www\.office.com  won't see the branding. After users sign in, the branding may take at least 15 minutes to appear.
 

articles/active-directory/fundamentals/media/user-default-permissions/tenant-creation-restriction.png

@@ -66,7 +66,7 @@ You can restrict default permissions for member users in the following ways:
 The **Restrict non-admin users from creating tenants** option is shown [below](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/UserSettings)
 
 
-:::image type="content" source="media/user-default-permissions/tenant-creation.png" alt-text="Screenshot showing the option to **Restrict non-admins from creating tenants**":::
+:::image type="content" source="media/user-default-permissions/tenant-creation-restriction.png" alt-text="Screenshot showing the option to Restrict non-admins from creating tenants." lightbox="media/user-default-permissions/tenant-creation-restriction.png":::
 
 ## Restrict guest users' default permissions
 

articles/active-directory/fundamentals/media/user-default-permissions/tenant-creation.png

@@ -118,7 +118,7 @@ Update-AzVM -ResourceGroupName TestRG -VM $vm -IdentityType "UserAssigned" -Iden
 
 This section shows how to grant your user-assigned identity access to a Resource Group in Azure Resource Manager. Managed identities for Azure resources provide identities that your code can use to request access tokens to authenticate to resource APIs that support Azure AD authentication. In this tutorial, your code will access the Azure Resource Manager API.
 
-Before your code can access the API, you need to grant the identity access to a resource in Azure Resource Manager. In this case, the Resource Group in which the VM is contained. Update the value for `<SUBSCRIPTION ID>` as appropriate for your environment.
+Before your code can access the API, you need to grant the identity access to a resource in Azure Resource Manager. In this case, the Resource Group in which the VM is contained. Update the value for `<SUBSCRIPTIONID>` as appropriate for your environment.
 
 ```azurepowershell-interactive
 $spID = (Get-AzUserAssignedIdentity -ResourceGroupName myResourceGroupVM -Name ID1).principalid
@@ -128,8 +128,8 @@ New-AzRoleAssignment -ObjectId $spID -RoleDefinitionName "Reader" -Scope "/subsc
 The response contains details for the role assignment created, similar to the following example:
 
 ```azurepowershell
-RoleAssignmentId: /subscriptions/80c696ff-5efa-4909-a64d-f1b616f423ca/resourcegroups/myResourceGroupVM/providers/Microsoft.Authorization/roleAssignments/f9cc753d-265e-4434-ae19-0c3e2ead62ac
-Scope: /subscriptions/80c696ff-5efa-4909-a64d-f1b616f423ca/resourcegroups/myResourceGroupVM
+RoleAssignmentId: /subscriptions/<SUBSCRIPTIONID>/resourcegroups/myResourceGroupVM/providers/Microsoft.Authorization/roleAssignments/f9cc753d-265e-4434-ae19-0c3e2ead62ac
+Scope: /subscriptions/<SUBSCRIPTIONID>/resourcegroups/myResourceGroupVM
 DisplayName: ID1
 SignInName:
 RoleDefinitionName: Reader

articles/active-directory/fundamentals/users-default-permissions.md

@@ -27,34 +27,41 @@ Application Gateway provides several built‑in timing metrics related to the re
 
 - **Backend connect time**
 
-  Time spent establishing a connection with the backend application. 
+   *Aggregation type:Avg/Max*
 
-  This includes the network latency as well as the time taken by the backend server’s TCP stack to  establish new connections. For TLS, it also includes the time spent on handshake. 
+   Time spent establishing a connection with the backend application. 
+
+   This includes the network latency as well as the time taken by the backend server’s TCP stack to  establish new connections. For TLS, it also includes the time spent on handshake. 
 
 - **Backend first byte response time**
 
-  Time interval between start of establishing a connection to backend server and receiving the first byte of the response header. 
+   *Aggregation type:Avg/Max*
+
+   Time interval between start of establishing a connection to backend server and receiving the first byte of the response header. 
 
-  This approximates the sum of *Backend connect time*, time taken by the request to reach the backend from Application Gateway, time taken by backend application to respond (the time the server took to generate content, potentially fetch database queries), and the time taken by first byte
-  of the response to reach the Application Gateway from the backend.
+   This approximates the sum of *Backend connect time*, time taken by the request to reach the backend from Application Gateway, time taken by backend application to respond (the time the server took to generate content, potentially fetch database queries), and the time taken by first byte of the response to reach the Application Gateway from the backend.
 
 - **Backend last byte response time**
 
-  Time interval between start of establishing a connection to backend server and receiving the last byte of the response body. 
+   *Aggregation type:Avg/Max*
+
+   Time interval between start of establishing a connection to backend server and receiving the last byte of the response body. 
 
-  This approximates the sum of *Backend first byte response time* and data transfer time (this number may vary greatly depending on the size of objects requested and the latency of the server network).
+   This approximates the sum of *Backend first byte response time* and data transfer time (this number may vary greatly depending on the size of objects requested and the latency of the server network).
 
 - **Application gateway total time**
 
-  Average time that it takes for a request to be received, processed and its response to be sent. 
+   *Aggregation type:Avg/Max*
 
-  This is the interval from the time when Application Gateway receives the first byte of the HTTP request to the time when the last response byte has been sent to the client. This includes the processing time taken by Application Gateway, the *Backend last byte response time*, and the time taken by Application Gateway to send all the response.
+   This metric captures either the Average/Max time taken for a request to be received, processed and its response to be sent. 
 
-- **Client RTT**
+   This is the interval from the time when Application Gateway receives the first byte of the HTTP request to the time when the last response byte has been sent to the client. This includes the processing time taken by Application Gateway, the *Backend last byte response time*, and the time taken by Application Gateway to send all the response.
 
-  Average round trip time between clients and Application Gateway.
+- **Client RTT**
 
+   *Aggregation type:Avg/Max*
 
+   This metric captures the Average/Max round trip time between clients and Application Gateway.
 
 These metrics can be used to determine whether the observed slowdown is due to the client network, Application Gateway performance, the backend network and backend server TCP stack saturation, backend application performance, or large file size.
 

articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-ua-arm.md

@@ -0,0 +1,39 @@
+---
+title: Convert Map and Filled map visuals to an Azure Maps Visual 
+titleSuffix: Microsoft Azure Maps Power BI visual
+description: This article covers how to convert Map and Filled map visuals to an Azure Maps Visual.
+author: deniseatmicrosoft
+ms.author: limingchen 
+ms.date: 05/23/2023
+ms.topic: how-to
+ms.service: azure-maps
+services: azure-maps
+---
+
+# Convert Map and Filled map visuals to an Azure Maps Visual
+
+The Azure Maps Visual is now Generally Available, providing a streamlined and intuitive experience for working with your data.
+
+## How to convert your existing Map and Filled map visuals
+
+A conversion function is available in Power BI desktop to convert any existing Map and Filled map visuals to the new Azure Maps Visual.
+
+When opening a report with Map and Filled map visuals, you will see the following dialog giving you the option to upgrade to the new Azure Maps Visual:
+
+:::image type="content" source="media/power-bi-visual/introducing-azure-map-visual.png" alt-text="Screenshot showing the option to upgrade maps to the Azure Maps Visual.":::
+
+When selecting the **Upgrade maps** button, all Map and Filled map visuals in the current report are converted. You can also convert a specific Map or Filled Map Visual to an Azure Maps Visual in the Visual gallery.
+
+All settings associated with the original visuals are carried over to the new Azure Maps Visual, ensuring consistency in the migrated report.
+
+:::image type="content" source="media/power-bi-visual/the-new-azure-maps-visual.png" alt-text="Screenshot showing the Bubble chart Description automatically generated.":::
+
+> [!NOTE]
+> Due to differences in supported bubble size ranges between the two platforms, you may notice that some bubbles appear smaller on the converted Azure Maps visual compared to their original size in the Maps visual. This is because the maximum bubble size in Azure Maps is smaller than the maximum bubble size in Bing Maps. Bubble size differences can vary based on the visual dimension and the report's zoom level.
+
+The migration function streamlines the process of converting Map and Filled map visuals to Azure Maps Visuals, providing users with an efficient and easy-to-use solution.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Get started with Azure Maps Power BI visual](power-bi-visual-get-started.md)

articles/application-gateway/application-gateway-metrics.md

@@ -42,7 +42,7 @@ Table 2: Lag featurization for $h=1$ <a name="tbl:classic-lag-1"></a>
 | 3/1/2001   | 20    | 2/1/2001  | 10        | 1       |
 | 4/1/2001   | 30    | 3/1/2001  | 20        | 1       |
 | 5/1/2001   | 40    | 4/1/2001  | 30        | 1       |
-| 6/1/2001   | 50    | 4/1/2001  | 40        | 1       |
+| 6/1/2001   | 50    | 5/1/2001  | 40        | 1       |
 
 Table 2 is generated from Table 1 by shifting the $y_t$ column down by a single observation. We've added a column named `Origin` that has the dates that the lag features originate from. Next, we generate the lagging feature for the forecast horizon $h=2$ only.