Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-constrained-delegation-edit-conditions

Author: rolyon

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/language-support-policy.md

@@ -140,7 +140,7 @@ Tomcat 8.5 reached [End of Life as of March 31, 2024](https://tomcat.apache.org/
 
 While the runtimes are still available on Azure App Service, Azure won't apply security updates to Tomcat 8.5 or 10.0.
 
-When possible, migrate your applications to Tomcat 9.5 or Tomcat 10.1. Tomcat 9.5 and Tomcat 10.1 are available on Azure App Service. For more information, see the [official Tomcat site](https://tomcat.apache.org/whichversion.html).
+When possible, migrate your applications to Tomcat 9.0 or Tomcat 10.1. Tomcat 9.0 and Tomcat 10.1 are available on Azure App Service. For more information, see the [official Tomcat site](https://tomcat.apache.org/whichversion.html).
 
 Community support for Java 7 ended on July 29, 2022 and [Java 7 was retired from App Service](https://azure.microsoft.com/updates/transition-to-java-11-or-8-by-29-july-2022/). If you have a web app running on Java 7, upgrade to Java 8 or 11 immediately.
 

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-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).

articles/azure-monitor/ai-ops/investigator-overview.md

@@ -0,0 +1,57 @@
+---
+title:  Azure Monitor Investigator overview
+description: Learn about Microsoft Azure Monitor Investigator and how it can help troubleshoot incidents in Azure resources using AI.
+ms.date: 04/09/2024
+ms.topic: overview
+ms.service: azure-monitor
+ms.author: abbyweisberg
+author: AbbyMSFT
+ms.reviewer: yalavi
+
+#customer intent: To learn about Azure Monitor Investigator and how it can help me troubleshoot incidents in Azure resources.
+---
+
+# What is Azure Monitor Investigator (preview)?
+
+Azure Monitor Investigator (preview) is an AIOps solution designed to improve the way Site Reliability Engineers (SREs) and developers approach incidents. Investigator  simplifies the process of incident troubleshooting, enabling faster resolution of issues with your Azure resources and the workloads running on them. Azure Monitor Investigator uses Azure monitor data to scan for anomalies across all your Azure resources, so that you don't have to rely on manual investigation methods like sifting through static dashboards or executing predefined queries. Based on the metrics, such as specific clusters, regions, error codes, or operations dimensions and labels, Azure Monitor investigator provides SREs and developers with actionable insights and concrete leads for further investigation.
+
+These are the ways you can trigger an investigation:
+
+- When an Azure Monitor alert is triggered, you can start an investigation with a single click from the alert instance.
+- You can start an investigation from the notification that you receive when an alert is triggered, for all action types other than phone or SMS.
+- Using Azure Copilot, you can ask about resource issues, and trigger an investigation.
+
+The system presents a summary of the issue and outlines what we know, a possible explanation, and what can be done next.
+
+## Automate analysis with Azure Monitor Investigator (preview)
+Azure Monitor Investigator (preview) automates analysis to simplify the identification of anomalies across Azure resources and provides recommended next steps with the following capabilities:
+
+### Metric analysis
+- •	Scans the Azure resources in the investigation target and scope for anomalies in platform metrics and custom metrics.
+- Assigns scores to metrics that show a correlation with the incident start time.
+- Generates explanations for the incident by conducting sub-pattern analysis to explain anomalies based on metric dimensions or labels that generate the most impact. 
+- Groups and ranks explanations to present the most likely causes.
+
+### Actionable insights
+- Provides an issue summary with insights into what happened, the potential causes, and how to further investigate the issue.
+
+### Configurable scope
+Azure Monitor Investigator makes suggestions for which resources to analyze based on the scope of the investigation. The default scope of an investigation includes all metrics of the target resource. You can change the scope to include up to 5 resources.
+
+## Join the preview
+To enable access to Azure Monitor Investigator for your organization, and to take part in shaping its development, there's a one-time setup process per subscription.
+
+In line with our commitment to responsible AI, we're currently limiting access to Azure Monitor Investigator (preview). Access to Azure Monitor Investigator (Preview) requires a registration process and is currently only available to a select group of enterprise customers and partners. Customers interested in using Azure Monitor Investigator (Preview) must [complete a registration form to request access](https://forms.office.com/r/hW2QJhXE2N).
+
+Granting access to Azure Monitor Investigator (preview) is at the discretion of Microsoft, based on eligibility criteria and a vetting process. Customers must acknowledge that they have read and understand the terms of service specific to Azure Monitor Investigator (Preview) within Azure.
+
+Azure Monitor Investigator (preview) is available under the terms governing the subscription to Microsoft Azure. Customers should review these terms thoroughly as they have important information and conditions that govern the use of Azure Monitor Investigator (Preview).
+
+If you have any questions about gaining access, consult with your Azure administrator.
+
+Some features and functionalities may be considerably enhanced, changed, or added as the tool evolves based on user feedback and continued development.
+
+## Related content
+
+- Learn how to [use Azure Monitor Investigator for AIOps](investigate-alert-instance.md).
+- Review our [Responsible AI FAQ for Microsoft Azure Investigator](responsible-ai-faq.md).