Skip to content

Commit 2f0b853

Browse files
authored
Merge branch 'main' into fixsuggestions
2 parents f9485be + 78ceca4 commit 2f0b853

File tree

1,902 files changed

+25684
-15548
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,902 files changed

+25684
-15548
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.defender-for-iot.json

Lines changed: 31 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,35 @@
11
{
2-
"redirections": [
2+
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/defender-for-iot/device-builders/how-to-azure-rtos-security-module.md",
5+
"redirect_url": "/azure/defender-for-iot/device-builders/how-to-threadx-security-module",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path_from_root": "/articles/defender-for-iot/device-builders/iot-security-azure-rtos.md",
10+
"redirect_url": "/azure/defender-for-iot/device-builders/iot-security-threadx",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path_from_root": "/articles/defender-for-iot/device-builders/azure-rtos-security-module-api.md",
15+
"redirect_url": "/azure/defender-for-iot/device-builders/threadx-security-module-api",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path_from_root": "/articles/defender-for-iot/device-builders/concept-rtos-security-alerts-recommendations.md",
20+
"redirect_url": "/azure/defender-for-iot/device-builders/concept-threadx-security-alerts-recommendations",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path_from_root": "/articles/defender-for-iot/device-builders/concept-rtos-security-module.md",
25+
"redirect_url": "/azure/defender-for-iot/device-builders/concept-threadx-security-module",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path_from_root": "/articles/defender-for-iot/device-builders/how-to-rtos-security-module.md",
30+
"redirect_url": "/azure/defender-for-iot/device-builders/how-to-threadx-security-module",
31+
"redirect_document_id": false
32+
},
333
{
434
"source_path_from_root": "/articles/defender-for-iot/organizations/resources-manage-proprietary-protocols.md",
535
"redirect_url": "/azure/defender-for-iot/organizations/how-to-manage-individual-sensors#manage-custom-plugins-legacy",

.openpublishing.redirection.json

Lines changed: 28 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1712,12 +1712,22 @@
17121712
},
17131713
{
17141714
"source_path_from_root": "/articles/guides/developer/index.md",
1715-
"redirect_url": "/azure/guides/developer/azure-developer-guide",
1715+
"redirect_url": "/azure/developer/",
1716+
"redirect_document_id": false
1717+
},
1718+
{
1719+
"source_path_from_root": "/articles/guides/developer/azure-developer-guide.md",
1720+
"redirect_url": "/azure/developer/",
17161721
"redirect_document_id": false
17171722
},
17181723
{
17191724
"source_path_from_root": "/articles/guides/operations/index.md",
1720-
"redirect_url": "/azure/guides/operations/azure-operations-guide",
1725+
"redirect_url": "/azure/developer/intro/azure-developer-key-concepts",
1726+
"redirect_document_id": false
1727+
},
1728+
{
1729+
"source_path_from_root": "/articles/guides/operations/azure-operations-guide.md",
1730+
"redirect_url": "/azure/developer/intro/azure-developer-key-concepts",
17211731
"redirect_document_id": false
17221732
},
17231733
{
@@ -3839,9 +3849,19 @@
38393849
"redirect_url": "/azure/reliability/reliability-guidance-overview",
38403850
"redirect_document_id": false
38413851
},
3852+
{
3853+
"source_path_from_root": "/articles/aks/cluster-configuration.md",
3854+
"redirect_url": "/azure/aks/concepts-clusters-workloads",
3855+
"redirect_document_id": false
3856+
},
38423857
{
38433858
"source_path_from_root": "/articles/orbital/overview-analytics.md",
38443859
"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",
38453865
"redirect_document_id": false
38463866
},
38473867
{
@@ -3974,6 +3994,11 @@
39743994
"source_path_from_root":"/articles/container-instances/availability-zones.md",
39753995
"redirect_url":"/azure/reliability/reliability-containers",
39763996
"redirect_document_id":false
3977-
}
3997+
},
3998+
{
3999+
"source_path_from_root":"/articles/service-connector/quickstart-cli-aks-connection.md",
4000+
"redirect_url":"/azure/service-connector/quickstart-portal-aks-connection",
4001+
"redirect_document_id":false
4002+
}
39784003
]
39794004
}

.openpublishing.redirection.sentinel.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1089,6 +1089,11 @@
10891089
"source_path_from_root": "/articles/sentinel/notebooks-with-synapse-hunt.md",
10901090
"redirect_url": "/azure/sentinel/notebooks-hunt",
10911091
"redirect_document_id": false
1092+
},
1093+
{
1094+
"source_path_from_root": "/articles/sentinel/data-connectors/dns.md",
1095+
"redirect_url": "/azure/sentinel/data-connectors/windows-dns-events-via-ama",
1096+
"redirect_document_id": false
10921097
}
10931098
]
10941099
}

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/concept-accuracy-confidence.md

Lines changed: 7 additions & 6 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: conceptual
11-
ms.date: 02/29/2024
11+
ms.date: 04/16/2023
1212
ms.author: lajanuar
1313
---
1414

@@ -53,10 +53,11 @@ Field confidence indicates an estimated probability between 0 and 1 that the pre
5353
## Interpret accuracy and confidence scores for custom models
5454

5555
When interpreting the confidence score from a custom model, you should consider all the confidence scores returned from the model. Let's start with a list of all the confidence scores.
56-
1. **Document type confidence score**: The document type confidence is an indicator of closely the analyzed document resembleds documents in the training dataset. When the document type confidence is low, this is indicative of template or structural variations in the analyzed document. To improve the document type confidence, label a document with that specific variation and add it to your training dataset. Once the model is re-trained, it should be better equipped to handl that class of variations.
57-
2. **Field level confidence**: Each labled field extracted has an associated confidence score. This score reflects the model's confidence on the position of the value extracted. While evaluating the confidence you should also look at the underlying extraction confidence to generate a comprehensive confidence for the extracted result. Evaluate the OCR results for text extraction or selection marks depending on the field type to generate a composite confidence score for the field.
58-
3. **Word confidence score** Each word extracted within the document has an associated confidence score. The score represents the confidence of the transcription. The pages array contains an array of words, each word has an associated span and confidence. Spans from the custom field extracted values will match the spans of the extracted words.
59-
4. **Selection mark confidence score**: The pages array also contains an array of selection marks, each selection mark has a confidence score representing the confidence of the seletion mark and selection state detection. When a labeled field is a selection mark, the custom field selection confidence combined with the selection mark confidence is an accurate representation of the overall confidence that the field was extracted correctly.
56+
57+
1. **Document type confidence score**: The document type confidence is an indicator of closely the analyzed document resembles documents in the training dataset. When the document type confidence is low, it's indicative of template or structural variations in the analyzed document. To improve the document type confidence, label a document with that specific variation and add it to your training dataset. Once the model is retrained, it should be better equipped to handle that class of variations.
58+
2. **Field level confidence**: Each labeled field extracted has an associated confidence score. This score reflects the model's confidence on the position of the value extracted. While evaluating confidence scores, you should also look at the underlying extraction confidence to generate a comprehensive confidence for the extracted result. Evaluate the `OCR` results for text extraction or selection marks depending on the field type to generate a composite confidence score for the field.
59+
3. **Word confidence score** Each word extracted within the document has an associated confidence score. The score represents the confidence of the transcription. The pages array contains an array of words and each word has an associated span and confidence score. Spans from the custom field extracted values match the spans of the extracted words.
60+
4. **Selection mark confidence score**: The pages array also contains an array of selection marks. Each selection mark has a confidence score representing the confidence of the selection mark and selection state detection. When a labeled field has a selection mark, the custom field selection combined with the selection mark confidence is an accurate representation of overall confidence accuracy.
6061

6162
The following table demonstrates how to interpret both the accuracy and confidence scores to measure your custom model's performance.
6263

@@ -69,7 +70,7 @@ The following table demonstrates how to interpret both the accuracy and confiden
6970

7071
## Table, row, and cell confidence
7172

72-
With the addition of table, row and cell confidence with the ```2024-02-29-preview``` API, here are some common questions that should help with interpreting the table, row and cell scores:
73+
With the addition of table, row and cell confidence with the ```2024-02-29-preview``` API, here are some common questions that should help with interpreting the table, row, and cell scores:
7374

7475
**Q:** Is it possible to see a high confidence score for cells, but a low confidence score for the row?<br>
7576

0 commit comments

Comments
 (0)