Skip to content

Commit 2ce8c59

Browse files
ShawnJacksonShawnJackson
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ai-agents
2 parents d445888 + afce34a commit 2ce8c59

File tree

641 files changed

+6732
-3998
lines changed

Some content is hidden

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

641 files changed

+6732
-3998
lines changed

‎.openpublishing.publish.config.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -986,6 +986,12 @@
986986
"branch": "main",
987987
"branch_mapping": {}
988988
},
989+
{
990+
"path_to_root": "msdocs-app-service-sqldb-dotnetcore",
991+
"url": "https://github.com/Azure-Samples/msdocs-app-service-sqldb-dotnetcore",
992+
"branch": "main",
993+
"branch_mapping": {}
994+
},
989995
{
990996
"path_to_root": "azuresignalr-samples",
991997
"url": "https://github.com/aspnet/AzureSignalR-samples",

‎.openpublishing.redirection.json

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4193,11 +4193,17 @@
41934193
"redirect_url": "/azure",
41944194
"redirect_document_id": false
41954195
},
4196+
{
4197+
4198+
"source_path_from_root": "/articles/site-recovery/move-vaults-across-regions.md",
4199+
"redirect_url": "/azure/operational-excellence/relocation-site-recovery",
4200+
"redirect_document_id": false
4201+
},
41964202
{
41974203
"source_path_from_root": "/articles/defender-for-iot/organizations/tutorial-clearpass.md",
41984204
"redirect_url": "/azure/defender-for-iot/organizations/integrate-overview",
41994205
"redirect_document_id": false
42004206
}
4201-
4207+
42024208
]
42034209
}

‎articles/active-directory-b2c/whats-new-docs.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory business-to-customer (B2C)"
33
description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
4-
ms.date: 06/05/2024
4+
ms.date: 07/01/2024
55
ms.service: active-directory
66
ms.subservice: B2C
77
ms.topic: whats-new
@@ -19,6 +19,14 @@ manager: CelesteDG
1919

2020
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
2121

22+
## June 2024
23+
24+
### Updated articles
25+
26+
- [Define an OAuth2 custom error technical profile in an Azure Active Directory B2C custom policy](oauth2-error-technical-profile.md) - Error code updates
27+
- [Configure authentication in a sample Python web app by using Azure AD B2C](configure-authentication-sample-python-web-app.md) - Python version update
28+
29+
2230
## May 2024
2331

2432
### New articles
@@ -45,10 +53,3 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
4553
- [Localization string IDs](localization-string-ids.md) - CAPTCHA updates
4654
- [Page layout versions](page-layout.md) - CAPTCHA updates
4755

48-
## January 2024
49-
50-
### Updated articles
51-
52-
- [Tutorial: Configure Nok Nok Passport with Azure Active Directory B2C for passwordless FIDO2 authentication](partner-nok-nok.md) - Updated Nok Nok instructions
53-
- [Configure Transmit Security with Azure Active Directory B2C for passwordless authentication](partner-bindid.md) - Updated Transmit Security instructions
54-
- [About claim resolvers in Azure Active Directory B2C custom policies](claim-resolver-overview.md) - Updated claim resolvers and user journey

‎articles/ai-services/document-intelligence/containers/install-run.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,10 @@ The host is a x64-based computer that runs the Docker container. It can be a com
6666
* [Azure Container Instances](../../../container-instances/index.yml).
6767
* A [Kubernetes](https://kubernetes.io/) cluster deployed to [Azure Stack](/azure-stack/operator). For more information, see [Deploy Kubernetes to Azure Stack](/azure-stack/user/azure-stack-solution-template-kubernetes-deploy).
6868

69+
> [!NOTE]
70+
>
71+
> Note that Studio container cannot be deployed and run in Azure Kubernetes Service. Studio container is only supported to be run on local machine.
72+
6973
### Container requirements and recommendations
7074

7175
#### Required supporting containers

‎articles/ai-services/language-service/conversational-language-understanding/concepts/best-practices.md

Lines changed: 24 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ You also want to avoid mixing different schema designs. Do not build half of you
4343

4444
## Use standard training before advanced training
4545

46-
[Standard training](../how-to/train-model.md#training-modes) is free and faster than Advanced training, making it useful to quickly understand the effect of changing your training set or schema while building the model. Once you are satisfied with the schema, consider using advanced training to get the best AIQ out of your model.
46+
[Standard training](../how-to/train-model.md#training-modes) is free and faster than Advanced training, making it useful to quickly understand the effect of changing your training set or schema while building the model. Once you're satisfied with the schema, consider using advanced training to get the best AIQ out of your model.
4747

4848
## Use the evaluation feature
4949

@@ -73,17 +73,31 @@ To resolve this, you would label a learned component in your training data for a
7373
If you require the learned component, make sure that *ticket quantity* is only returned when the learned component predicts it in the right context. If you also require the prebuilt component, you can then guarantee that the returned *ticket quantity* entity is both a number and in the correct position.
7474

7575

76-
## Addressing casing inconsistencies
76+
## Addressing model inconsistencies
7777

78-
If you have poor AI quality and determine the casing used in your training data is dissimilar to the testing data, you can use the `normalizeCasing` project setting. This normalizes the casing of utterances when training and testing the model. If you've migrated from LUIS, you might recognize that LUIS did this by default.
78+
If your model is overly sensitive to small grammatical changes, like casing or diacritics, you can systematically manipulate your dataset directly in the Language Studio. To use these features, click on the Settings tab on the left toolbar and locate the **Advanced project settings** section. First, you can ***Enable data transformation for casing***, which normalizes the casing of utterances when training, testing, and implementing your model. If you've migrated from LUIS, you might recognize that LUIS did this normalization by default. To access this feature via the API, set the `"normalizeCasing"` parameter to `true`. See an example below:
7979

8080
```json
8181
{
8282
"projectFileVersion": "2022-10-01-preview",
8383
...
8484
"settings": {
85-
"confidenceThreshold": 0.5,
85+
...
8686
"normalizeCasing": true
87+
...
88+
}
89+
...
90+
```
91+
Second, you can also leverage the **Advanced project settings** to ***Enable data augmentation for diacritics*** to generate variations of your training data for possible diacritic variations used in natural language. This feature is available for all languages, but it is especially useful for Germanic and Slavic languages, where users often write words using classic English characters instead of the correct characters. For example, the phrase "Navigate to the sports channel" in French is "Accédez à la chaîne sportive". When this feature is enabled, the phrase "Accedez a la chaine sportive" (without diacritic characters) is also included in the training dataset. If you enable this feature, please note that the utterance count of your training set will increase, and you may need to adjust your training data size accordingly. The current maximum utterance count after augmentation is 25,000. To access this feature via the API, set the `"augmentDiacritics"` parameter to `true`. See an example below:
92+
93+
```json
94+
{
95+
"projectFileVersion": "2022-10-01-preview",
96+
...
97+
"settings": {
98+
...
99+
"augmentDiacritics": true
100+
...
87101
}
88102
...
89103
```
@@ -125,9 +139,9 @@ Once the request is sent, you can track the progress of the training job in Lang
125139

126140
Model version 2023-04-15, conversational language understanding provides normalization in the inference layer that doesn't affect training.
127141

128-
The normalization layer normalizes the classification confidence scores to a confined range. The range selected currently is from `[-a,a]` where "a" is the square root of the number of intents. As a result, the normalization depends on the number of intents in the app. If there is a very low number of intents, the normalization layer has a very small range to work with. With a fairly large number of intents, the normalization is more effective.
142+
The normalization layer normalizes the classification confidence scores to a confined range. The range selected currently is from `[-a,a]` where "a" is the square root of the number of intents. As a result, the normalization depends on the number of intents in the app. If there's a very low number of intents, the normalization layer has a very small range to work with. With a fairly large number of intents, the normalization is more effective.
129143

130-
If this normalization doesn’t seem to help intents that are out of scope to the extent that the confidence threshold can be used to filter out of scope utterances, it might be related to the number of intents in the app. Consider adding more intents to the app, or if you are using an orchestrated architecture, consider merging apps that belong to the same domain together.
144+
If this normalization doesn’t seem to help intents that are out of scope to the extent that the confidence threshold can be used to filter out of scope utterances, it might be related to the number of intents in the app. Consider adding more intents to the app, or if you're using an orchestrated architecture, consider merging apps that belong to the same domain together.
131145

132146
## Debugging composed entities
133147

@@ -146,7 +160,7 @@ Data in a conversational language understanding project can have two data sets.
146160

147161
## Custom parameters for target apps and child apps
148162

149-
If you are using [orchestrated apps](./app-architecture.md), you may want to send custom parameter overrides for various child apps. The `targetProjectParameters` field allows users to send a dictionary representing the parameters for each target project. For example, consider an orchestrator app named `Orchestrator` orchestrating between a conversational language understanding app named `CLU1` and a custom question answering app named `CQA1`. If you want to send a parameter named "top" to the question answering app, you can use the above parameter.
163+
If you're using [orchestrated apps](./app-architecture.md), you may want to send custom parameter overrides for various child apps. The `targetProjectParameters` field allows users to send a dictionary representing the parameters for each target project. For example, consider an orchestrator app named `Orchestrator` orchestrating between a conversational language understanding app named `CLU1` and a custom question answering app named `CQA1`. If you want to send a parameter named "top" to the question answering app, you can use the above parameter.
150164

151165
```console
152166
curl --request POST \
@@ -249,6 +263,6 @@ curl --location 'https://<your-resource>.cognitiveservices.azure.com/language/au
249263
Once the request is sent, you can track the progress of the training job in Language Studio as usual.
250264

251265
Caveats:
252-
- The None Score threshold for the app (confidence threshold below which the topIntent is marked as None) when using this recipe should be set to 0. This is because this new recipe attributes a certain portion of the in domain probabiliities to out of domain so that the model is not incorrectly overconfident about in domain utterances. As a result, users may see slightly reduced confidence scores for in domain utterances as compared to the prod recipe.
253-
- This recipe is not recommended for apps with just two (2) intents, such as IntentA and None, for example.
254-
- This recipe is not recommended for apps with low number of utterances per intent. A minimum of 25 utterances per intent is highly recommended.
266+
- The None Score threshold for the app (confidence threshold below which the topIntent is marked as None) when using this recipe should be set to 0. This is because this new recipe attributes a certain portion of the in domain probabilities to out of domain so that the model isn't incorrectly overconfident about in domain utterances. As a result, users may see slightly reduced confidence scores for in domain utterances as compared to the prod recipe.
267+
- This recipe isn't recommended for apps with just two (2) intents, such as IntentA and None, for example.
268+
- This recipe isn't recommended for apps with low number of utterances per intent. A minimum of 25 utterances per intent is highly recommended.

‎articles/ai-services/language-service/question-answering/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: language-service-question-answering
1414
# What is custom question answering?
1515

1616
> [!NOTE]
17-
> [Azure Open AI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to Custom Question Answering. If you wish to connect an existing Custom Question Answering project to Azure Open AI On Your Data, please check out our [guide]( how-to/azure-openai-integration.md).
17+
> [Azure OpenAI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to Custom Question Answering. If you wish to connect an existing Custom Question Answering project to Azure OpenAI On Your Data, please check out our [guide]( how-to/azure-openai-integration.md).
1818
1919
Custom question answering provides cloud-based Natural Language Processing (NLP) that allows you to create a natural conversational layer over your data. It is used to find appropriate answers from customer input or from a project.
2020

‎articles/ai-services/language-service/question-answering/tutorials/active-learning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ This tutorial shows you how to enhance your custom question answering project wi
2424

2525
These variations when added as alternate questions to the relevant question answer pair, help to optimize the project to answer real world user queries. You can manually add alternate questions to question answer pairs through the editor. At the same time, you can also use the active learning feature to generate active learning suggestions based on user queries. The active learning feature, however, requires that the project receives regular user traffic to generate suggestions.
2626

27-
## Enable active learning
27+
## Use active learning
2828

2929
Active learning is turned on by default for custom question answering enabled resources.
3030

‎articles/ai-services/language-service/summarization/language-support.md

Lines changed: 34 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,24 @@ Use this article to learn which natural languages are supported by document and
1818

1919
## Text and document summarization
2020

21-
Extractive and abstractive text summarization as well as document summarization support the following languages:
21+
Extractive text and document summarization support the following languages:
22+
23+
| Language | Language code | Notes |
24+
|-----------------------|---------------|---------------------|
25+
| Chinese-Simplified | `zh-hans` | `zh` also accepted |
26+
| English | `en` | |
27+
| French | `fr` | |
28+
| German | `de` | |
29+
| Hebrew | `he` | |
30+
| Italian | `it` | |
31+
| Japanese | `ja` | |
32+
| Korean | `ko` | |
33+
| Polish | `pl` | |
34+
| Portuguese (Portugal) | `pt` | |
35+
| Portuguese (Brazil) | `pt-br` | |
36+
| Spanish | `es` | |
37+
38+
Abstractive text and document summarization support the following languages:
2239

2340
| Language | Language code | Notes |
2441
|-----------------------|---------------|---------------------|
@@ -32,7 +49,8 @@ Extractive and abstractive text summarization as well as document summarization
3249
| Japanese | `ja` | |
3350
| Korean | `ko` | |
3451
| Polish | `pl` | |
35-
| Portuguese | `pt` | |
52+
| Portuguese (Portugal) | `pt` | |
53+
| Portuguese (Brazil) | `pt-br` | |
3654
| Spanish | `es` | |
3755

3856
## Conversation summarization
@@ -42,6 +60,7 @@ Conversation summarization supports the following languages:
4260
| Language | Language code | Notes |
4361
|-----------------------|---------------|---------------------|
4462
| Chinese-Simplified | `zh-hans` | `zh` also accepted |
63+
| Chinese-Traditional | `zh-hant` | |
4564
| English | `en` | |
4665
| French | `fr` | |
4766
| German | `de` | |
@@ -50,7 +69,19 @@ Conversation summarization supports the following languages:
5069
| Japanese | `ja` | |
5170
| Korean | `ko` | |
5271
| Polish | `pl` | |
53-
| Portuguese | `pt` | |
72+
| Portuguese (Portugal) | `pt` | |
73+
| Portuguese (Brazil) | `pt-br` | |
74+
| Dutch, Flemish | `nl` | |
75+
| Swedish | `sv` | |
76+
| Danish | `da` | |
77+
| Finnish | `fi` | |
78+
| Russian | `ru` | |
79+
| Norwegian | `no` | |
80+
| Turkish | `tr` | |
81+
| Arabic | `ar` | |
82+
| Czech | `cs` | |
83+
| Hungarian | `hu` | |
84+
| Thai | `th` | |
5485
| Spanish | `es` | |
5586

5687
## Custom summarization

‎articles/ai-services/openai/api-version-deprecation.md

Lines changed: 2 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: cognitive-services
55
manager: nitinme
66
ms.service: azure-ai-openai
77
ms.topic: conceptual
8-
ms.date: 05/20/2024
8+
ms.date: 07/01/2024
99
author: mrbullwinkle
1010
ms.author: mbullwin
1111
recommendations: false
@@ -14,7 +14,7 @@ ms.custom:
1414

1515
# Azure OpenAI API preview lifecycle
1616

17-
This article is to help you understand the support lifecycle for the Azure OpenAI API previews. New preview APIs target a monthly release cadence. After July 1, 2024, the latest three preview APIs will remain supported while older APIs will no longer be supported unless support is explicitly indicated.
17+
This article is to help you understand the support lifecycle for the Azure OpenAI API previews. New preview APIs target a monthly release cadence. After February 3rd, 2025, the latest three preview APIs will remain supported while older APIs will no longer be supported unless support is explicitly indicated.
1818

1919
> [!NOTE]
2020
> The `2023-06-01-preview` API will remain supported at this time, as `DALL-E 2` is only available in this API version. `DALL-E 3` is supported in the latest API releases. The `2023-10-01-preview` API will also remain supported at this time.
@@ -59,18 +59,6 @@ is currently the latest GA API release. This API version is the replacement for
5959

6060
This version contains support for the latest GA features like Whisper, DALL-E 3, fine-tuning, on your data, etc. Any preview features that were released after the `2023-12-01-preview` release like Assistants, TTS, certain on your data datasources, are only supported in the latest preview API releases.
6161

62-
## Retiring soon
63-
64-
On July 1, 2024 the following API preview releases will be retired and will stop accepting API requests:
65-
66-
- 2023-03-15-preview
67-
- 2023-07-01-preview
68-
- 2023-08-01-preview
69-
- 2023-09-01-preview
70-
- 2023-12-01-preview
71-
72-
To avoid service disruptions, you must update to use the latest preview version before the retirement date.
73-
7462
## Updating API versions
7563

7664
We recommend first testing the upgrade to new API versions to confirm there's no impact to your application from the API update before making the change globally across your environment.

0 commit comments

Comments
 (0)