Merge pull request #298476 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-maps/how-to-view-api-usage.md

@@ -1,7 +1,7 @@
 ---
 title: View Azure Maps API usage metrics
 titleSuffix: Microsoft Azure Maps
-description: Learn how to view Azure Maps API usage metrics, such as total requests, total errors, and availability. See how to filter data and split results.
+description: Discover how to monitor Azure Maps API usage metrics, including total requests, total errors, and availability. Learn how to filter data and break down results for better insights.
 author: sinnypan
 ms.author: sipa
 ms.date: 03/31/2025
@@ -12,15 +12,15 @@ ms.subservice: general
 
 # View Azure Maps API usage metrics
 
-This article shows you how to view the API usage metrics, for your Azure Maps account, in the [Azure portal]. The metrics are shown in a convenient graph format along a customizable time duration.
+This article guides you on how to view API usage metrics for your Azure Maps account in the [Azure portal]. The metrics are displayed in an easy-to-read graph format over a customizable time period.
 
 ## View metric snapshot
 
-You can see some common metrics on the **Overview** page of your Maps account. It currently shows *Total Requests*, *Total Errors*, and *Availability* over a selectable time duration.
+The **Overview** page of your Maps account displays key metrics such as *Total Requests*, *Total Errors*, and *Availability* over a selectable time period.
 
 ![Azure Maps usage metrics overview](media/how-to-view-api-usage/portal-overview.png)
 
-Continue to the next section if you need to customize these graphs for your particular analysis.
+Proceed to the next section to customize these graphs for your specific analysis needs.
 
 ## View detailed metrics
 
@@ -30,30 +30,34 @@ Continue to the next section if you need to customize these graphs for your part
 
 3. Once your Maps account is open, select the **Metrics** menu on the left.
 
-4. On the **Metrics** pane, choose one of the following options:
+4. In the **Metrics** pane, choose one of the following options:
 
-   1. **Availability** - which shows the *Average* of API availability over a period of time.
-   2. **Usage** - which shows how the usage *Count* for your account.
+   1. **Availability** - displays the Average API availability over a specified time period.
+   2. **Usage** - displays the usage count for your account.
 
       ![Azure Maps usage metrics pane](media/how-to-view-api-usage/portal-metrics.png)
 
-5. Next, you may select the *Time range* by selecting **Last 24 hours (Automatic)**. By default, the time range is set to 24 hours. After clicking, you'll see all selectable time ranges. You can select the *Time granularity* and choose to show the time as *local* or *GMT* in the same drop-down. Click **Apply**.
+5. The default time range is **Last 24 hours (Automatic)**. To change this, select the default value to open the _Time Range_ pop-up, which displays all available settings. You can change the *Time granularity* and show the time as *local* or *GMT*. Once the desired options are chosen, select **Apply**.
 
     ![Azure Maps metrics time range](media/how-to-view-api-usage/time-range.png)
 
-6. Once you add your metric, you can **Add filter** from the properties relevant to that metric. Then, select the value of the property that you want to see reflected on the graph.
+    > [!NOTE]
+    > Metrics are stored for 93 days, but you can only query up to 30 days' worth of data at a time. If you encounter a blank chart or partial metric data, ensure the start and end dates in the time picker don't exceed a 30-day interval. Once you've selected a 30-day interval, you can pan the chart to view other metrics. For more information, see [Troubleshooting metrics charts](/azure/azure-monitor/essentials/data-platform-metrics).
+
+6. After adding your metric, you can apply a filter based on the properties relevant to that metric. Then, choose the value of the property you want to display on the graph.
 
     ![Azure Maps usage metrics Filter](media/how-to-view-api-usage/filter.png)
 
-7. You may also **Apply splitting** for your metric based on your selected metric property. It allows the graph to be split into multiple graphs, for each value of that property. In the following picture, the color of each graph corresponds to the property value shown at the bottom of the graph.
+7. You can also **Apply splitting** for your metric based on your selected metric property. This feature allows the graph to be divided into multiple graphs, each representing a different value of that property. In the following example, the color of each graph corresponds to the property value displayed at the bottom.
 
     ![Azure Maps usage metrics splitting](media/how-to-view-api-usage/splitting.png)
 
-8. You may also observe multiple metrics on the same graph, by selecting the **Add metric** button.
+8. You can also view multiple metrics on the same graph by selecting the **Add metric** button.
 
 ## Next steps
 
-Learn more about the Azure Maps APIs you want to track usage for:
+Discover more about the Azure Maps APIs you wish to monitor:
+
 > [!div class="nextstepaction"]
 > [Azure Maps Web SDK How-To]
 

articles/azure-maps/understanding-azure-maps-transactions.md

@@ -22,7 +22,7 @@ When you use [Azure Maps Services], the API requests you make generate transac
 
 ## Azure Maps Transaction information by service
 
-The following table summarizes the Azure Maps services that generate transactions, billable and nonbillable, along with any notable aspects that are helpful to understand in how the number of transactions are calculated.
+The following table summarizes the Azure Maps services that generate both billable and nonbillable transactions, along with key aspects to help understand how the number of transactions is calculated.
 
 > [!NOTE]
 >
@@ -33,7 +33,7 @@ The following table summarizes the Azure Maps services that generate transaction
 | [Data registry] (Deprecated<sup>1</sup>) | Yes      | One request = 1 transaction| <ul><li>Location Insights Data (Gen2 pricing)</li></ul>|
 | [Geolocation]| Yes| One request = 1 transaction| <ul><li>Location Insights Geolocation (Gen2 pricing)</li><li>Standard S1 Geolocation Transactions (Gen1 S1 pricing)</li><li>Standard Geolocation Transactions (Gen1 S0 pricing)</li></ul>|
 | [Render] | Yes, except Get Copyright API, Get Attribution API and Terra maps (`MapTile.GetTerraTile` and `layer=terra`) which are nonbillable.|<ul><li>15 tiles = 1 transaction</li><li>One request for Get Copyright = 1 transaction</li><li>One request for Get Map Attribution = 1 transaction</li><li>One request for Get Static Map = 1 transaction</li><li>One request for Get Map Tileset = 1 transaction</li></ul> <br> For Creator related usage, see the [Creator table]. |<ul><li>Maps Base Map Tiles (Gen2 pricing)</li><li>Maps Imagery Tiles (Gen2 pricing)</li><li>Maps Static Map Images (Gen2 pricing)</li><li>Maps Weather Tiles (Gen2 pricing)</li><li>Standard Hybrid Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard S1 Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Hybrid Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Rendering Transactions (Gen1 S1 pricing)</li><li>Standard S1 Tile Transactions (Gen1 S1 pricing)</li><li>Standard S1 Weather Tile Transactions (Gen1 S1 pricing)</li><li>Standard Tile Transactions (Gen1 S0 pricing)</li><li>Standard Weather Tile Transactions (Gen1 S0 pricing)</li><li>Maps Copyright (Gen2 pricing, Gen1 S0 pricing and Gen1 S1 pricing)</li></ul>|
-| [Route] | Yes | One request = 1 transaction<br><ul><li>If using the Route Matrix, every four cells in the Route Matrix request generates a billable Route transaction, rounded up to the nearest whole number. If you provided 5 origins and 10 destinations, that would be counted as `Ceiling(0.25*5*10) = 13` Routing transactions.</li><li>If using Batch Directions, each route query (route origin/destination coordinate pair and waypoints) in the Batch request call generates a billable Route transaction. Note, the billable Route transaction usage results generated by the batch request has **-Batch** appended to the API name of your Azure portal metrics report.</li></ul> | <ul><li>Location Insights Routing (Gen2 pricing)</li><li>Standard S1 Routing Transactions (Gen1 S1 pricing)</li><li>Standard Services API Transactions (Gen1 S0 pricing)</li></ul> |
+| [Route] | Yes | One request = 1 transaction<br><ul><li>If using the Route Matrix, every four cells in the Route Matrix request generates a billable Route transaction, rounded up to the nearest whole number. If you provided 5 origins and 10 destinations, that would be counted as `Ceiling(0.25*5*10) = 13` Routing transactions.</li><li>If using **Batch transactions**, each query in the Batch request call generates a billable Route transaction.</li><li>If using **Snap to Roads**. Snap to Roads is billed similarly to other Route APIs: 1 request equals 1 transaction, and each request can support up to 100 snap-to-roads points.</li></ul> | <ul><li>Location Insights Routing (Gen2 pricing)</li><li>Standard S1 Routing Transactions (Gen1 S1 pricing)</li><li>Standard Services API Transactions (Gen1 S0 pricing)</li></ul> |
 | [Search v1]<br>[Search v2] | Yes | One request = 1 transaction.<br><ul><li>If using Batch Search, each location in the Batch request generates a billable Search transaction. Note, the billable Search transaction usage results generated by the batch request has **-Batch** appended to the API name of your Azure portal metrics report.</li></ul> | <ul><li>Location Insights Search</li><li>Standard S1 Search Transactions (Gen1 S1 pricing)</li><li>Standard Services API Transactions (Gen1 S0 pricing)</li></ul> |
 | [Spatial] (Deprecated<sup>1</sup>) | Yes, except for `Spatial.GetBoundingBox`, `Spatial.PostBoundingBox` and `Spatial.PostPointInPolygonBatch`, which are nonbillable.| One request = 1 transaction.<br><ul><li>If using Geofence, five requests = 1 transaction</li></ul> | <ul><li>Location Insights Spatial Calculations (Gen2 pricing)</li><li>Standard S1 Spatial Transactions (Gen1 S1 pricing)</li></ul> |
 | [Timezone] | Yes | One request = 1 transaction | <ul><li>Location Insights Timezone (Gen2 pricing)</li><li>Standard S1 Time Zones Transactions (Gen1 S1 pricing)</li><li>Standard Time Zones Transactions (Gen1 S0 pricing)</li></ul> |
@@ -44,11 +44,11 @@ The following table summarizes the Azure Maps services that generate transaction
 
 > [!NOTE]
 >
-> There is no charge to use [Azure Maps Power BI visual](power-bi-visual-get-started.md) as long as you have a [Power BI subscription](/power-bi/fundamentals/service-self-service-signup-for-power-bi).
+> There's no charge to use [Azure Maps Power BI visual](power-bi-visual-get-started.md) as long as you have a [Power BI subscription](/power-bi/fundamentals/service-self-service-signup-for-power-bi).
 
 > [!TIP]
 >
-> Unlike Bing Maps, Azure Maps doesn’t use [session IDs]. Instead, Azure Maps offers a number of free transactions each month as shown in [Azure Maps pricing]. For example, you get 5,000 free *Base Map Tile* transactions per month. Each transaction can include up to 15 tiles for a total of 75,000 tiles rendered for free each month.
+> Unlike Bing Maps, Azure Maps doesn’t use [session IDs]. Instead, Azure Maps offers many free transactions each month as shown in [Azure Maps pricing]. For example, you get 5,000 free *Base Map Tile* transactions per month. Each transaction can include up to 15 tiles for a total of 75,000 tiles rendered for free each month.
 <!-- In Bing Maps, any time a synchronous Truck Routing request is made, three transactions are counted. Does this apply also to Azure Maps?-->
 
 ## Azure Maps Creator

articles/communication-services/how-tos/call-automation/includes/secure-webhook-endpoint-csharp.md

@@ -18,9 +18,9 @@ Each mid-call webhook callback sent by Call Automation uses a signed JSON Web To
 1. Obtain the Open ID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
 2. Install the [Microsoft.AspNetCore.Authentication.JwtBearer NuGet](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.JwtBearer) package.
 3. Configure your application to validate the JWT using the NuGet package and the configuration of your Azure Communication Services resource. You need the `audience` values as it is present in the JWT payload.
-4. Validate the issuer, audience and the JWT token.
+4. Validate the issuer, audience and the JWT.
    - The audience is your Azure Communication Services resource ID you used to set up your Call Automation client. Refer [here](../../../quickstarts/voice-video-calling/get-resource-id.md) about how to get it.
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys used to validate the JWT token. When the signature is valid and the token hasn't expired (within 5 minutes of generation), the client can use the token for authorization.
+   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys used to validate the JWT. When the signature is valid and the token hasn't expired (within 5 minutes of generation), the client can use the token for authorization.
 
 This sample code demonstrates how to use `Microsoft.IdentityModel.Protocols.OpenIdConnect` to validate webhook payload
 

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

@@ -72,7 +72,7 @@ Includes more details about using Azure KeyVault. No audio, demonstration only w
 
 We recommend creating a dedicated virtual machine for your data connector agent container to ensure optimal performance and avoid potential conflicts. For more information, see [System prerequisites for the data connector agent container](prerequisites-for-deploying-sap-continuous-threat-monitoring.md#system-prerequisites-for-the-data-connector-agent-container).
 
-We recommend that you store your SAP and authentication secrets in an [Azure key vault](/azure/key-vault/general/authentication). How you access your key vault depends on where your virtual machine (VM) is deployed:
+We recommend that you store your SAP and authentication secrets in an [Azure Key Vault](/azure/key-vault/general/authentication). How you access your key vault depends on where your virtual machine (VM) is deployed:
 
 |Deployment method  |Access method  |
 |---------|---------|
@@ -324,7 +324,7 @@ While deployment is also supported from the command line, we recommend that you
 
 1. Review the settings you defined. Select **Previous** to modify any settings, or select **Deploy** to deploy the system.
 
-The system configuration you defined is deployed into the Azure key vault you defined during the deployment. You can now see the system details in the table under **Configure an SAP system and assign it to a collector agent**. This table displays the associated agent name, SAP System ID (SID), and health status for systems that you added via the portal or otherwise.
+The system configuration you defined is deployed into the Azure Key Vault you defined during the deployment. You can now see the system details in the table under **Configure an SAP system and assign it to a collector agent**. This table displays the associated agent name, SAP System ID (SID), and health status for systems that you added via the portal or otherwise.
 
 At this stage, the system's **Health** status is **Pending**. If the agent is updated successfully, it pulls the configuration from Azure Key vault, and the status changes to **System healthy**. This update can take up to 10 minutes.