Skip to content

Commit 9142797

Browse files
committed
resolve conflict
2 parents 8a4f554 + eca2853 commit 9142797

File tree

1,250 files changed

+15010
-8685
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,250 files changed

+15010
-8685
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6664,6 +6664,21 @@
66646664
"redirect_url": "/azure/azure-monitor/monitor-azure-monitor-reference",
66656665
"redirect_document_id": false
66666666
},
6667+
{
6668+
"source_path_from_root": "/articles/azure-monitor/ai-ops/responsible-ai-faq.md",
6669+
"redirect_url": "/azure/copilot/overview",
6670+
"redirect_document_id": false
6671+
},
6672+
{
6673+
"source_path_from_root": "/articles/azure-monitor/ai-ops/investigator-overview.md",
6674+
"redirect_url": "/azure/copilot/overview",
6675+
"redirect_document_id": false
6676+
},
6677+
{
6678+
"source_path_from_root": "/articles/azure-monitor/ai-ops/investigate-alert-instance.md",
6679+
"redirect_url": "/azure/copilot/overview",
6680+
"redirect_document_id": false
6681+
},
66676682
{
66686683
"source_path_from_root": "/articles/azure-monitor/azure-monitor-monitoring-reference.md",
66696684
"redirect_url": "/azure/azure-monitor/monitor-azure-monitor-reference",
@@ -6688,7 +6703,18 @@
66886703
"source_path_from_root": "/articles/azure-monitor/agents/resource-manager-data-collection-rules.md",
66896704
"redirect_url": "/azure/azure-monitor/essentials/data-collection-rule-create-edit?tabs=arm#manually-create-a-dcr",
66906705
"redirect_document_id": false
6706+
},
6707+
{
6708+
"source_path_from_root": "/articles/azure-monitor/essentials/remote-write-prometheus.md",
6709+
"redirect_url": "/azure/azure-monitor/essentials/prometheus-remote-write-virtual-machines",
6710+
"redirect_document_id": false
6711+
},
6712+
{
6713+
"source_path_from_root": "/articles/azure-monitor/essentials/prometheus-get-started.md",
6714+
"redirect_url": "/azure/azure-monitor/essentials/prometheus-metrics-overview",
6715+
"redirect_document_id": false
66916716
}
6717+
66926718

66936719
]
66946720
}

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3857,6 +3857,11 @@
38573857
{
38583858
"source_path_from_root": "/articles/orbital/overview-analytics.md",
38593859
"redirect_url": "/azure/orbital/overview",
3860+
"redirect_document_id": false
3861+
},
3862+
{
3863+
"source_path_from_root": "/articles/aks/intro-kubernetes.md",
3864+
"redirect_url": "/azure/aks/what-is-aks",
38603865
"redirect_document_id": false
38613866
},
38623867
{

articles/advisor/advisor-how-to-calculate-total-cost-savings.md

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,15 @@
11
---
2-
title: Export cost savings in Azure Advisor
2+
title: Calculate cost savings in Azure Advisor
33
ms.topic: article
44
ms.date: 02/06/2024
55
description: Export cost savings in Azure Advisor and calculate the aggregated potential yearly savings by using the cost savings amount for each recommendation.
66
---
77

8-
# Export cost savings
8+
# Calculate cost savings
9+
10+
This article provides guidance on how to calculate total cost savings in Azure Advisor.
11+
12+
## Export cost savings for recommendations
913

1014
To calculate aggregated potential yearly savings, follow these steps:
1115

@@ -21,5 +25,14 @@ The Advisor **Overview** page opens.
2125
[![Screenshot of the Azure Advisor cost recommendations page that shows download option.](./media/advisor-how-to-calculate-total-cost-savings.png)](./media/advisor-how-to-calculate-total-cost-savings.png#lightbox)
2226

2327
> [!NOTE]
24-
> Recommendations show savings individually, and may overlap with the savings shown in other recommendations, for example – you can only benefit from savings plans for compute or reservations for virtual machines, but not from both.
28+
> Different types of cost savings recommendations are generated using overlapping datasets (for example, VM rightsizing/shutdown, VM reservations and savings plan recommendations all consider on-demand VM usage). As a result, resource changes (e.g., VM shutdowns) or reservation/savings plan purchases will impact on-demand usage, and the resulting recommendations and associated savings forecast.
29+
30+
## Understand cost savings
31+
32+
Azure Advisor provides recommendations for resizing/shutting down underutilized resources, purchasing compute reserved instances, and savings plans for compute.
33+
34+
These recommendations contain one or more calls-to-action and forecasted savings from following the recommendations. Recommendations should be followed in a specific order: rightsizing/shutdown, followed by reservation purchases, and finally, the savings plan purchase. This sequence allows each step to impact the subsequent ones positively.
35+
36+
For example, rightsizing or shutting down resources reduces on-demand costs immediately. This change in your usage pattern essentially invalidates your existing reservation and savings plan recommendations, as they were based on your pre-rightsizing usage and costs. Updated reservation and savings plan recommendations (and their forecasted savings) should appear within three days.
2537

38+
The forecasted savings from reservations and savings plans are based on actual rates and usage, while the forecasted savings from rightsizing/shutdown are based on retail rates. The actual savings may vary depending on the usage patterns and rates. Assuming there are no material changes to your usage patterns, your actual savings from reservations and savings plan should be in line with the forecasts. Savings from rightsizing/shutdown vary based on your actual rates. This is important if you intend to track cost savings forecasts from Azure Advisor.

articles/advisor/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@
7474
href: advisor-azure-resource-graph.md
7575
- name: Consume Advisor score
7676
href: azure-advisor-score.md
77-
- name: Export cost savings
77+
- name: Calculate total cost savings
7878
href: advisor-how-to-calculate-total-cost-savings.md
7979
- name: Reference
8080
items:

articles/ai-services/document-intelligence/disaster-recovery.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: azure-ai-document-intelligence
88
ms.custom:
99
- ignite-2023
1010
ms.topic: how-to
11-
ms.date: 03/06/2024
11+
ms.date: 04/17/2024
1212
ms.author: lajanuar
1313
---
1414

@@ -65,7 +65,7 @@ The process for copying a custom model consists of the following steps:
6565
The following HTTP request gets copy authorization from your target resource. You need to enter the endpoint and key of your target resource as headers.
6666

6767
```http
68-
POST https://<your-resource-name>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
68+
POST https://<your-resource-endpoint>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
6969
Ocp-Apim-Subscription-Key: {<your-key>}
7070
```
7171

@@ -96,7 +96,7 @@ You receive a `200` response code with response body that contains the JSON payl
9696
The following HTTP request starts the copy operation on the source resource. You need to enter the endpoint and key of your source resource as the url and header. Notice that the request URL contains the model ID of the source model you want to copy.
9797

9898
```http
99-
POST https://<your-resource-name>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
99+
POST https://<your-resource-endpoint>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview
100100
Ocp-Apim-Subscription-Key: {<your-key>}
101101
```
102102

@@ -117,7 +117,7 @@ You receive a `202\Accepted` response with an Operation-Location header. This va
117117

118118
```http
119119
HTTP/1.1 202 Accepted
120-
Operation-Location: https://<your-resource-name>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
120+
Operation-Location: https://<your-resource-endpoint>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
121121
```
122122

123123
> [!NOTE]
@@ -126,7 +126,7 @@ Operation-Location: https://<your-resource-name>.cognitiveservices.azure.com/doc
126126
## Track Copy progress
127127

128128
```console
129-
GET https://<your-resource-name>.cognitiveservices.azure.com/documentintelligence/operations/{<operation-id>}?api-version=2024-02-29-preview
129+
GET https://<your-resource-endpoint>.cognitiveservices.azure.com/documentintelligence/operations/{<operation-id>}?api-version=2024-02-29-preview
130130
Ocp-Apim-Subscription-Key: {<your-key>}
131131
```
132132

@@ -135,7 +135,7 @@ Ocp-Apim-Subscription-Key: {<your-key>}
135135
You can also use the **[Get model](/rest/api/aiservices/document-models/get-model?view=rest-aiservices-2023-07-31&preserve-view=true&tabs=HTTP)** API to track the status of the operation by querying the target model. Call the API using the target model ID that you copied down from the [Generate Copy authorization request](#generate-copy-authorization-request) response.
136136

137137
```http
138-
GET https://<your-resource-name>/documentintelligence/documentModels/{modelId}?api-version=2024-02-29-preview" -H "Ocp-Apim-Subscription-Key: <your-key>
138+
GET https://<your-resource-endpoint>/documentintelligence/documentModels/{modelId}?api-version=2024-02-29-preview" -H "Ocp-Apim-Subscription-Key: <your-key>
139139
```
140140

141141
In the response body, you see information about the model. Check the `"status"` field for the status of the model.
@@ -155,7 +155,7 @@ The following code snippets use cURL to make API calls. You also need to fill in
155155
**Request**
156156

157157
```bash
158-
curl -i -X POST "<your-resource-name>/documentintelligence/documentModels:authorizeCopy?api-version=2024-02-29-preview"
158+
curl -i -X POST "<your-resource-endpoint>/documentintelligence/documentModels:authorizeCopy?api-version=2024-02-29-preview"
159159
-H "Content-Type: application/json"
160160
-H "Ocp-Apim-Subscription-Key: <YOUR-KEY>"
161161
--data-ascii "{
@@ -182,7 +182,7 @@ curl -i -X POST "<your-resource-name>/documentintelligence/documentModels:author
182182
**Request**
183183

184184
```bash
185-
curl -i -X POST "<your-resource-name>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview"
185+
curl -i -X POST "<your-resource-endpoint>/documentintelligence/documentModels/{modelId}:copyTo?api-version=2024-02-29-preview"
186186
-H "Content-Type: application/json"
187187
-H "Ocp-Apim-Subscription-Key: <YOUR-KEY>"
188188
--data-ascii "{
@@ -200,7 +200,7 @@ curl -i -X POST "<your-resource-name>/documentintelligence/documentModels/{model
200200

201201
```http
202202
HTTP/1.1 202 Accepted
203-
Operation-Location: https://<your-resource-name>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
203+
Operation-Location: https://<your-resource-endpoint>.cognitiveservices.azure.com/documentintelligence/operations/{operation-id}?api-version=2024-02-29-preview
204204
```
205205

206206
### Track copy operation progress

articles/ai-services/openai/concepts/models.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure OpenAI
44
description: Learn about the different model capabilities that are available with Azure OpenAI.
55
ms.service: azure-ai-openai
66
ms.topic: conceptual
7-
ms.date: 04/15/2024
7+
ms.date: 04/17/2024
88
ms.custom: references_regions, build-2023, build-2023-dataai, refefences_regions
99
manager: nitinme
1010
author: mrbullwinkle #ChrisHMSFT
@@ -92,6 +92,8 @@ You can also use the OpenAI text to speech voices via Azure AI Speech. To learn
9292

9393
[!INCLUDE [Standard Models](../includes/model-matrix/standard-models.md)]
9494

95+
This table does not include fine-tuning regional availability, consult the dedicated [fine-tuning section](#fine-tuning-models) for this information.
96+
9597
### Standard deployment model quota
9698

9799
[!INCLUDE [Quota](../includes/model-matrix/quota.md)]
@@ -237,15 +239,15 @@ The following Embeddings models are available with [Azure Government](/azure/azu
237239

238240
`babbage-002` and `davinci-002` are not trained to follow instructions. Querying these base models should only be done as a point of reference to a fine-tuned version to evaluate the progress of your training.
239241

240-
`gpt-35-turbo-0613` - fine-tuning of this model is limited to a subset of regions, and is not available in every region the base model is available.
242+
`gpt-35-turbo` - fine-tuning of this model is limited to a subset of regions, and is not available in every region the base model is available.
241243

242244
| Model ID | Fine-Tuning Regions | Max Request (tokens) | Training Data (up to) |
243245
| --- | --- | :---: | :---: |
244-
| `babbage-002` | North Central US <br> Sweden Central | 16,384 | Sep 2021 |
245-
| `davinci-002` | North Central US <br> Sweden Central | 16,384 | Sep 2021 |
246-
| `gpt-35-turbo` (0613) | East US2 <br> North Central US <br> Sweden Central | 4,096 | Sep 2021 |
247-
| `gpt-35-turbo` (1106) | East US2 <br> North Central US <br> Sweden Central | Input: 16,385<br> Output: 4,096 | Sep 2021|
248-
| `gpt-35-turbo` (0125) | East US2 <br> North Central US <br> Sweden Central | 16,385 | Sep 2021 |
246+
| `babbage-002` | North Central US <br> Sweden Central <br> Switzerland West | 16,384 | Sep 2021 |
247+
| `davinci-002` | North Central US <br> Sweden Central <br> Switzerland West | 16,384 | Sep 2021 |
248+
| `gpt-35-turbo` (0613) | East US2 <br> North Central US <br> Sweden Central <br> Switzerland West | 4,096 | Sep 2021 |
249+
| `gpt-35-turbo` (1106) | East US2 <br> North Central US <br> Sweden Central <br> Switzerland West | Input: 16,385<br> Output: 4,096 | Sep 2021|
250+
| `gpt-35-turbo` (0125) | East US2 <br> North Central US <br> Sweden Central <br> Switzerland West | 16,385 | Sep 2021 |
249251

250252
### Whisper models
251253

articles/ai-services/openai/how-to/content-filters.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: Learn how to use content filters (preview) with Azure OpenAI Servic
66
manager: nitinme
77
ms.service: azure-ai-openai
88
ms.topic: how-to
9-
ms.date: 03/29/2024
9+
ms.date: 04/16/2024
1010
author: mrbullwinkle
1111
ms.author: mbullwin
1212
recommendations: false
@@ -15,7 +15,7 @@ recommendations: false
1515
# How to configure content filters with Azure OpenAI Service
1616

1717
> [!NOTE]
18-
> All customers have the ability to modify the content filters to be stricter (for example, to filter content at lower severity levels than the default). Approval is required for turning the content filters partially or fully off. Managed customers only may apply for full content filtering control via this form: [Azure OpenAI Limited Access Review: Modified Content Filters](https://ncv.microsoft.com/uEfCgnITdR).
18+
> All customers have the ability to modify the content filters and configure the severity thresholds (low, medium, high). Approval is required for turning the content filters partially or fully off. Managed customers only may apply for full content filtering control via this form: [Azure OpenAI Limited Access Review: Modified Content Filters](https://ncv.microsoft.com/uEfCgnITdR).
1919
2020
The content filtering system integrated into Azure OpenAI Service runs alongside the core models and uses an ensemble of multi-class classification models to detect four categories of harmful content (violence, hate, sexual, and self-harm) at four severity levels respectively (safe, low, medium, and high), and optional binary classifiers for detecting jailbreak risk, existing text, and code in public repositories. The default content filtering configuration is set to filter at the medium severity threshold for all four content harms categories for both prompts and completions. That means that content that is detected at severity level medium or high is filtered, while content detected at severity level low or safe is not filtered by the content filters. Learn more about content categories, severity levels, and the behavior of the content filtering system [here](../concepts/content-filter.md). Jailbreak risk detection and protected text and code models are optional and off by default. For jailbreak and protected material text and code models, the configurability feature allows all customers to turn the models on and off. The models are by default off and can be turned on per your scenario. Some models are required to be on for certain scenarios to retain coverage under the [Customer Copyright Commitment](/legal/cognitive-services/openai/customer-copyright-commitment?context=%2Fazure%2Fai-services%2Fopenai%2Fcontext%2Fcontext).
2121

articles/ai-services/openai/includes/fine-tuning-python.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,17 @@ If you would like a step-by-step walk-through of fine-tuning a `gpt-35-turbo-061
7575
{"messages": [{"role": "system", "content": "You are an Xbox customer support agent whose primary goal is to help users with issues they are experiencing with their Xbox devices. You are friendly and concise. You only provide factual answers to queries, and do not provide answers that are not related to Xbox."}, {"role": "user", "content": "I'm having trouble connecting my Xbox to the Wi-Fi."}, {"role": "assistant", "content": "No worries, let's go through the network settings on your Xbox. Can you please tell me what happens when you try to connect it to the Wi-Fi?"}]}
7676
```
7777

78-
In addition to the JSONL format, training and validation data files must be encoded in UTF-8 and include a byte-order mark (BOM). The file must be less than 100 MB in size.
78+
### Multi-turn chat file format
79+
80+
Multiple turns of a conversation in a single line of your jsonl training file is also supported. To skip fine-tuning on specific assistant messages add the optional `weight` key value pair. Currently `weight` can be set to 0 or 1.
81+
82+
```json
83+
{"messages": [{"role": "system", "content": "Marv is a factual chatbot that is also sarcastic."}, {"role": "user", "content": "What's the capital of France?"}, {"role": "assistant", "content": "Paris", "weight": 0}, {"role": "user", "content": "Can you be more sarcastic?"}, {"role": "assistant", "content": "Paris, as if everyone doesn't know that already.", "weight": 1}]}
84+
{"messages": [{"role": "system", "content": "Marv is a factual chatbot that is also sarcastic."}, {"role": "user", "content": "Who wrote 'Romeo and Juliet'?"}, {"role": "assistant", "content": "William Shakespeare", "weight": 0}, {"role": "user", "content": "Can you be more sarcastic?"}, {"role": "assistant", "content": "Oh, just some guy named William Shakespeare. Ever heard of him?", "weight": 1}]}
85+
{"messages": [{"role": "system", "content": "Marv is a factual chatbot that is also sarcastic."}, {"role": "user", "content": "How far is the Moon from Earth?"}, {"role": "assistant", "content": "384,400 kilometers", "weight": 0}, {"role": "user", "content": "Can you be more sarcastic?"}, {"role": "assistant", "content": "Around 384,400 kilometers. Give or take a few, like that really matters.", "weight": 1}]}
86+
```
87+
88+
In addition to the JSONL format, training and validation data files must be encoded in UTF-8 and include a byte-order mark (BOM). The file must be less than 512 MB in size.
7989

8090
### Create your training and validation datasets
8191

@@ -93,7 +103,7 @@ The training and validation data you use **must** be formatted as a JSON Lines (
93103
{"prompt": "<prompt text>", "completion": "<ideal generated text>"}
94104
```
95105

96-
In addition to the JSONL format, training and validation data files must be encoded in UTF-8 and include a byte-order mark (BOM). The file must be less than 100 MB in size.
106+
In addition to the JSONL format, training and validation data files must be encoded in UTF-8 and include a byte-order mark (BOM). The file must be less than 512 MB in size.
97107

98108
### Create your training and validation datasets
99109

@@ -263,7 +273,7 @@ print(response)
263273

264274
---
265275

266-
You can also pass additional optional parameters like hyperparameters to take greater control of the fine-tuning process. For initial training we recommend using the automatic defaults that are present without specifying these parameters.
276+
You can also pass additional optional parameters like hyperparameters to take greater control of the fine-tuning process. For initial training we recommend using the automatic defaults that are present without specifying these parameters.
267277

268278
The current supported hyperparameters for fine-tuning are:
269279

0 commit comments

Comments
 (0)