Merge pull request #272313 from MicrosoftDocs/main

4/16/2024 AM Publish

Author: Taojunshen

articles/ai-services/openai/how-to/latency.md

@@ -59,7 +59,7 @@ Latency varies based on what model you're using. For an identical request, expec
 When you send a completion request to the Azure OpenAI endpoint, your input text is converted to tokens that are then sent to your deployed model. The model receives the input tokens and then begins generating a response. It's an iterative sequential process, one token at a time. Another way to think of it is like a for loop with `n tokens = n iterations`. For most models, generating the response is the slowest step in the process.  
 
 At the time of the request, the requested generation size (max_tokens parameter) is used as an initial estimate of the generation size. The compute-time for generating the full size is reserved by the model as the request is processed. Once the generation is completed, the remaining quota is released. Ways to reduce the number of tokens:
-- Set the `max_token` parameter on each call as small as possible.
+- Set the `max_tokens` parameter on each call as small as possible.
 - Include stop sequences to prevent generating extra content.
 - Generate fewer responses: The best_of & n parameters can greatly increase latency because they generate multiple outputs. For the fastest response, either don't specify these values or set them to 1.
 
@@ -136,4 +136,4 @@ Time from the first token to the last token, divided by the number of generated
 
 * **Streaming**: Enabling streaming can be useful in managing user expectations in certain situations by allowing the user to see the model response as it is being generated rather than having to wait until the last token is ready.
 
-* **Content Filtering** improves safety, but it also impacts latency. Evaluate if any of your workloads would benefit from [modified content filtering policies](./content-filters.md).
+* **Content Filtering** improves safety, but it also impacts latency. Evaluate if any of your workloads would benefit from [modified content filtering policies](./content-filters.md).

articles/app-service/reference-app-settings.md

@@ -33,7 +33,7 @@ The following environment variables are related to the app environment in genera
 | `WEBSITE_NPM_DEFAULT_VERSION` | Default npm version the app is using. ||
 | `WEBSOCKET_CONCURRENT_REQUEST_LIMIT` | Read-only. Limit for websocket's concurrent requests. For **Standard** tier and above, the value is `-1`, but there's still a per VM limit based on your VM size (see [Cross VM Numerical Limits](https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#cross-vm-numerical-limits)). ||
 | `WEBSITE_PRIVATE_EXTENSIONS` | Set to `0` to disable the use of private site extensions. ||
-| `WEBSITE_TIME_ZONE` | By default, the time zone for the app is always UTC. You can change it to any of the valid values that are listed in [TimeZone](/previous-versions/windows/it-pro/windows-vista/cc749073(v=ws.10)). If the specified value isn't recognized, UTC is used. | `Atlantic Standard Time` |
+| `WEBSITE_TIME_ZONE` | By default, the time zone for the app is always UTC. You can change it to any of the valid values that are listed in [Default Time Zones](/windows-hardware/manufacture/desktop/default-time-zones). If the specified value isn't recognized, UTC is used. | `Atlantic Standard Time` |
 | `WEBSITE_ADD_SITENAME_BINDINGS_IN_APPHOST_CONFIG` | After slot swaps, the app may experience unexpected restarts. This is because after a swap, the hostname binding configuration goes out of sync, which by itself doesn't cause restarts. However, certain underlying storage events (such as storage volume failovers) may detect these discrepancies and force all worker processes to restart. To minimize these types of restarts, set the app setting value to `1`on all slots (default is`0`). However, don't set this value if you're running a Windows Communication Foundation (WCF) application. For more information, see [Troubleshoot swaps](deploy-staging-slots.md#troubleshoot-swaps)||
 | `WEBSITE_PROACTIVE_AUTOHEAL_ENABLED` | By default, a VM instance is proactively "autohealed" when it's using more than 90% of allocated memory for more than 30 seconds, or when 80% of the total requests in the last two minutes take longer than 200 seconds. If a VM instance has triggered one of these rules, the recovery process is an overlapping restart of the instance. Set to `false` to disable this recovery behavior. The default is `true`. For more information, see [Proactive Auto Heal](https://azure.github.io/AppService/2017/08/17/Introducing-Proactive-Auto-Heal.html). ||
 | `WEBSITE_PROACTIVE_CRASHMONITORING_ENABLED` | Whenever the w3wp.exe process on a VM instance of your app crashes due to an unhandled exception for more than three times in 24 hours, a debugger process is attached to the main worker process on that instance, and collects a memory dump when the worker process crashes again. This memory dump is then analyzed and the call stack of the thread that caused the crash is logged in your App Service’s logs. Set to `false` to disable this automatic monitoring behavior. The default is `true`. For more information, see [Proactive Crash Monitoring](https://azure.github.io/AppService/2021/03/01/Proactive-Crash-Monitoring-in-Azure-App-Service.html). ||

articles/azure-arc/data/update-service-principal-credentials.md

@@ -7,16 +7,20 @@ ms.subservice: azure-arc-data
 author: AbdullahMSFT
 ms.author: amamun
 ms.reviewer: mikeray
-ms.date: 07/30/2021
+ms.date: 04/16/2024
 ms.topic: how-to
 ---
 
 # Update service principal credentials
 
-When the service principal credentials change, you need to update the secrets in the data controller.
+This article explains how to update the secrets in the data controller.
 
-For example, if you deployed the data controller using a specific set of values for service principal tenant ID, client ID, and client secret, and then change one or more of these values, you need to update the secrets in the data controller.  Following are the instructions to update Tenant ID, Client ID or the Client secret. 
+For example, if you:
 
+- Deployed the data controller using a specific set of values for service principal tenant ID, client ID, and client secret
+- Change one or more of these values
+
+You need to update the secrets in the data controller. 
 
 ## Background
 
@@ -36,7 +40,7 @@ The service principal was created at [Create service principal](upload-metrics-a
    kubectl edit secret/upload-service-principal-secret -n arc
    ```
 
-   The `kubecl edit` command opens the credentials .yml file in the default editor. 
+   The `kubectl edit` command opens the credentials .yml file in the default editor. 
 
 
 1. Edit the service principal secret. 
@@ -52,18 +56,18 @@ The service principal was created at [Create service principal](upload-metrics-a
    #
    apiVersion: v1
    data:
-     authority: aHR0cHM6Ly9sb2dpbi5taWNyb3NvZnRvbmxpbmUuY29t
-     clientId: NDNiNDcwYrFTGWYzOC00ODhkLTk0ZDYtNTc0MTdkN2YxM2Uw
-     clientSecret: VFA2RH125XU2MF9+VVhXenZTZVdLdECXFlNKZi00Lm9NSw==
-     tenantId: NzJmOTg4YmYtODZmMRFVBGTJLSATkxYWItMmQ3Y2QwMTFkYjQ3
+     authority: <authority id>
+     clientId: <client id>
+     clientSecret: <client secret>==
+     tenantId: <tenant id>
    kind: Secret
    metadata:
      creationTimestamp: "2020-12-02T05:02:04Z"
      name: upload-service-principal-secret
      namespace: arc
      resourceVersion: "7235659"
      selfLink: /api/v1/namespaces/arc/secrets/upload-service-principal-secret
-     uid: 7fb693ff-6caa-4a31-b83e-9bf22be4c112
+     uid: <globally unique identifier>
    type: Opaque
    ```
 
@@ -73,14 +77,12 @@ The service principal was created at [Create service principal](upload-metrics-a
 >The values need to be base64 encoded. 
 Do not edit any other properties.
 
-If an incorrect value is provided for `clientId`, `clientSecret` or `tenantID` then you will see an error message as follows in the `control-xxxx` pod/controller container logs:
+If an incorrect value is provided for `clientId`, `clientSecret`, or `tenantID` the command returns an error message as follows in the `control-xxxx` pod/controller container logs:
 
 ```output
-YYYY-MM-DD HH:MM:SS.mmmm | ERROR | [AzureUpload] Upload task exception: A configuration issue is preventing authentication - check the error message from the server for details.You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details.  Original exception: AADSTS7000215: Invalid client secret is provided.
+YYYY-MM-DD HH:MM:SS.mmmm | ERROR | [AzureUpload] Upload task exception: A configuration issue is preventing authentication - check the error message from the server for details.You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details. Original exception: AADSTS7000215: Invalid client secret is provided.
 ```
 
-
-
 ## Related content
 
-[Create service principal](upload-metrics-and-logs-to-azure-monitor.md#create-service-principal)
+- [Create service principal](upload-metrics-and-logs-to-azure-monitor.md#create-service-principal)

articles/azure-arc/data/upload-metrics-and-logs-to-azure-monitor.md

@@ -8,7 +8,7 @@ ms.custom: devx-track-azurecli
 author: twright-msft
 ms.author: twright
 ms.reviewer: mikeray
-ms.date: 11/03/2021
+ms.date: 04/16/2024
 ms.topic: how-to
 ---
 
@@ -72,20 +72,20 @@ az ad sp credential reset --name <ServicePrincipalName>
 For example, to create a service principal named `azure-arc-metrics`, run the following command
 
 ```azurecli
-az ad sp create-for-rbac --name azure-arc-metrics --role Contributor --scopes /subscriptions/a345c178a-845a-6a5g-56a9-ff1b456123z2/resourceGroups/myresourcegroup
+az ad sp create-for-rbac --name azure-arc-metrics --role Contributor --scopes /subscriptions/<SubscriptionId>/resourceGroups/myresourcegroup
 ```
 
 Example output:
 
 ```output
-"appId": "2e72adbf-de57-4c25-b90d-2f73f126e123",
+"appId": "<appId>",
 "displayName": "azure-arc-metrics",
 "name": "http://azure-arc-metrics",
-"password": "5039d676-23f9-416c-9534-3bd6afc78123",
-"tenant": "72f988bf-85f1-41af-91ab-2d7cd01ad1234"
+"password": "<password>",
+"tenant": "<tenant>"
 ```
 
-Save the `appId`, `password`, and `tenant` values in an environment variable for use later. 
+Save the `appId`, `password`, and `tenant` values in an environment variable for use later. These values are in the form of globally unique identifier (GUID).
 
 # [Windows](#tab/windows)
 
@@ -148,11 +148,11 @@ Example output:
 ```output
 {
   "canDelegate": null,
-  "id": "/subscriptions/<Subscription ID>/providers/Microsoft.Authorization/roleAssignments/f82b7dc6-17bd-4e78-93a1-3fb733b912d",
-  "name": "f82b7dc6-17bd-4e78-93a1-3fb733b9d123",
-  "principalId": "5901025f-0353-4e33-aeb1-d814dbc5d123",
+  "id": "/subscriptions/<Subscription ID>/providers/Microsoft.Authorization/roleAssignments/<globally unique identifier>",
+  "name": "<globally unique identifier>",
+  "principalId": "<principal id>",
   "principalType": "ServicePrincipal",
-  "roleDefinitionId": "/subscriptions/<Subscription ID>/providers/Microsoft.Authorization/roleDefinitions/3913510d-42f4-4e42-8a64-420c39005123",
+  "roleDefinitionId": "/subscriptions/<Subscription ID>/providers/Microsoft.Authorization/roleDefinitions/<globally unique identifier>",
   "scope": "/subscriptions/<Subscription ID>",
   "type": "Microsoft.Authorization/roleAssignments"
 }

articles/azure-maps/power-bi-visual-add-tile-layer.md

@@ -40,7 +40,7 @@ There are three different tile service naming conventions supported by the Azure
 
 * **X, Y, Zoom notation** - X is the column, Y is the row position of the tile in the tile grid, and the Zoom notation a value based on the zoom level.
 * **Quadkey notation** - Combines x, y, and zoom information into a single string value. This string value becomes a unique identifier for a single tile.
-* **Bounding Box** - Specify an image in the Bounding box coordinates format: `{west},{south},{east},{north}`. This format is commonly used by [Web Mapping Services (WMS)].
+* **Bounding Box** - Specify an image in the Bounding box coordinates format: `{west},{south},{east},{north}`.
 
 The tile URL an https URL to a tile URL template that uses the following
 parameters:
@@ -54,7 +54,7 @@ parameters:
 As an example, here's a formatted tile URL for the [weather radar tile service] in Azure Maps.
 
 ```html
-`https://atlas.microsoft.com/map/tile?zoom={z}&x={x}&y={y}&tilesetId=microsoft.weather.radar.main&api-version=2.0&subscription-key={Your-Azure-Maps-Subscription-key}`
+https://atlas.microsoft.com/map/tile?zoom={z}&x={x}&y={y}&tilesetId=microsoft.weather.radar.main&api-version=2.0&subscription-key={Your-Azure-Maps-Subscription-key}
 ```
 
 For more information on Azure Maps tiling system, see [Zoom levels and tile grid].
@@ -66,7 +66,6 @@ Add more context to the map:
 > [!div class="nextstepaction"]
 > [Show real-time traffic]
 
-[Web Mapping Services (WMS)]: https://www.opengeospatial.org/standards/wms
 [Show real-time traffic]: power-bi-visual-show-real-time-traffic.md
 [Zoom levels and tile grid]: zoom-levels-and-tile-grid.md
 [weather radar tile service]: /rest/api/maps/render/get-map-tile

articles/azure-monitor/agents/resource-manager-agent.md

@@ -1068,9 +1068,6 @@ resource managedIdentity 'Microsoft.Compute/virtualMachines/extensions@2021-11-0
       },
       "workspaceResourceId": {
         "value": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourcegroups/my-resource-group/providers/microsoft.operationalinsights/workspaces/my-workspace"
-      },
-      "workspaceKey": {
-        "value": "Npl#3y4SmqG4R30ukKo3oxfixZ5axv1xocXgKR17kgVdtacU4cEf+SNr2TdHGVKTsZHZv3R8QKRXfh+ToVR9dA-="
       }
   }
 }

articles/azure-monitor/ai-ops/investigate-alert-instance.md

@@ -0,0 +1,51 @@
+---
+title: Investigate an incident with Azure Monitor Investigator
+description: Learn how to use the Azure Monitor investigator to use AIOps to investigate an incident using AI.
+ms.author: abbyweisberg
+author: MSFT
+ms.topic: how-to
+ms.date: 04/09/2024
+ms.reviewer: yalavi
+
+# Customer intent: As a Site Reliability Engineer (SRE), developer, or IT operations engineer, I want to know how to use AI to explain why an alert was fired and tell me what my next steps should be to resolve the issue.
+---
+
+# Use AIOps to investigate incidents Azure Monitor Investigator
+
+This article describes how to use Azure Monitor Investigator to trigger an investigation to identify resource issues, or to explain why an alert was fired, and provide next steps to resolve the issue.
+
+## Investigate an alert
+
+1. From the home page in the [Azure portal](https://portal.azure.com/), select **Monitor** > **Alerts**.
+1. From the **Alerts** page, select the alert that you want to investigate.
+1. In the alert details pane, select **Investigate** on the top right.
+
+    :::image type="content" source="./media/investigate-alert-instance/investigate-button.png" alt-text="Screenshot of the investigate button from the alert details page.":::
+
+1. Alternatively, you can select **Investigate** from the email notification about an alert.
+1. The investigation starts to run. 
+
+    :::image type="content" source="./media/investigate-alert-instance/investigator-running.png" alt-text="Screenshot of the investigator in the middle of running.":::
+
+1. When the investigation is complete, a summary of the incident is displayed with recommendations for how to mitigate the issue.
+
+    :::image type="content" source="./media/investigate-alert-instance/investigator-response.png" alt-text="Screenshot of the investigator response with recommendations.":::
+
+
+## Ask Copilot to trigger an investigation
+
+1. From the home page in the [Azure portal](https://portal.azure.com/), select **Copilot**.
+1. In **Copilot**, ask about resource issues to get more insight into the issue. Here are some examples of questions you can ask:
+    - "Is there any anomaly in my edge resource?"
+    - "Run anomaly detection for the last two days."
+    - "Any anomaly on my AKS resource?"
+    - "Had an alert in my HCI at 8 am this morning, run an anomaly investigation for me"
+    - "Run anomaly detection at 2023-10-27T20:48:53Z."
+    - "Run anomaly detection at 10/27/2023, 8:48:53 PM"
+ 
+1.  Copilot runs an investigation and respond with the results.
+
+
+## Next steps
+
+Learn about [Responsible AI for Azure Monitor Investigator](responsible-ai-faq.md).