Skip to content

Commit ec7795d

Browse files
diberrydiberry
committed
Merge branch 'diberry/1022-js-entra-use-your-data' of https://github.com/diberry/azure-ai-docs-pr into diberry/1022-js-entra-use-your-data
2 parents a4dc18b + 223d23d commit ec7795d

File tree

308 files changed

+5241
-2623
lines changed

Some content is hidden

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

308 files changed

+5241
-2623
lines changed

‎.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,21 @@
99
"source_path_from_root": "/articles/search/search-howto-create-indexers.md",
1010
"redirect_url": "/azure/search/search-how-to-create-indexers",
1111
"redirect_document_id": false
12+
},
13+
{
14+
"source_path_from_root": "/articles/search/search-howto-dotnet-sdk.md",
15+
"redirect_url": "/azure/search/search-how-to-dotnet-sdk",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path_from_root": "/articles/search/search-howto-index-csv-blobs.md",
20+
"redirect_url": "/azure/search/search-how-to-index-csv-blobs",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path_from_root": "/articles/search/search-howto-large-index.md",
25+
"redirect_url": "/azure/search/search-how-to-large-index",
26+
"redirect_document_id": false
1227
}
1328
]
1429
}

‎articles/ai-services/.openpublishing.redirection.ai-services.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -769,6 +769,16 @@
769769
"source_path_from_root": "/articles/ai-services/speech-service/video-translation-studio.md",
770770
"redirect_url": "/azure/ai-services/speech-service/video-translation-get-started",
771771
"redirect_document_id": true
772+
},
773+
{
774+
"source_path_from_root": "/articles/ai-services/qnamaker/how-to/migrate-to-openai.md",
775+
"redirect_url": "/azure/ai-services/qnamaker/overview/overview",
776+
"redirect_document_id": true
777+
},
778+
{
779+
"source_path_from_root": "/articles/ai-services/language-service/question-answering/how-to/azure-openai-integration.md",
780+
"redirect_url": "/azure/ai-services/language-service/question-answering/overview",
781+
"redirect_document_id": true
772782
}
773783
]
774784
}

‎articles/ai-services/computer-vision/how-to/identity-access-token.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,10 @@ Independent software vendors (ISVs) can manage the Face API usage of their clien
1919

2020
This guide shows you how to generate the access tokens, if you're an approved ISV, and how to use the tokens if you're a client.
2121

22-
The limited access token feature is a part of the existing Azure AI Services token service. We have added a new operation for the purpose of bypassing the Limited Access gate for approved scenarios. Only ISVs that pass the gating requirements will be given access to this feature.
22+
The limited access token feature is a part of the existing Azure AI Services token service. We have added a new operation for the purpose of bypassing the Limited Access gate for approved scenarios.
23+
24+
> [!IMPORTANT]
25+
> Only ISVs that pass the gating requirements will be given access to this feature. To request approval, contact [[email protected]](mailto:[email protected]).
2326
2427
## Example use case
2528

@@ -60,7 +63,7 @@ curl -X POST 'https://<isv-endpoint>/sts/v1.0/issueLimitedAccessToken?expiredTim
6063
-H 'Ocp-Apim-Subscription-Key: <isv-face-key>' \
6164
-H 'Content-Type: application/json' \
6265
-d '{
63-
"resourceId": "/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.CognitiveServices/accounts/<face-resource-name>",
66+
"targetAzureResourceId": "/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.CognitiveServices/accounts/<face-resource-name>",
6467
"featureFlags": ["Face.Identification", "Face.Verification"]
6568
}'
6669
```

‎articles/ai-services/computer-vision/includes/quickstarts-sdk/identity-java-sdk.md

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -51,19 +51,7 @@ Get started with facial recognition using the Face client library for Java. Foll
5151
<dependency>
5252
<groupId>com.azure</groupId>
5353
<artifactId>azure-ai-vision-face</artifactId>
54-
<version>1.0.0-beta.1</version>
55-
</dependency>
56-
<!-- https://mvnrepository.com/artifact/org.apache.httpcomponents/httpclient -->
57-
<dependency>
58-
<groupId>org.apache.httpcomponents</groupId>
59-
<artifactId>httpclient</artifactId>
60-
<version>4.5.13</version>
61-
</dependency>
62-
<!-- https://mvnrepository.com/artifact/com.google.code.gson/gson -->
63-
<dependency>
64-
<groupId>com.google.code.gson</groupId>
65-
<artifactId>gson</artifactId>
66-
<version>2.11.0</version>
54+
<version>1.0.0-beta.2</version>
6755
</dependency>
6856
</dependencies>
6957
</project>

‎articles/ai-services/computer-vision/overview-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ The goal of liveness detection is to ensure that the system is interacting with
8282

8383
The liveness detection solution successfully defends against a variety of spoof types ranging from paper printouts, 2d/3d masks, and spoof presentations on phones and laptops. Liveness detection is an active area of research, with continuous improvements being made to counteract increasingly sophisticated spoofing attacks over time. Continuous improvements will be rolled out to the client and the service components over time as the overall solution gets more robust to new types of attacks.
8484

85-
Our liveness detection solution meets iBeta Level 1 and 2 ISO/IEC 30107-3 compliance.
85+
Our liveness detection solution meets [iBeta Level 1 and 2 ISO/IEC 30107-3](https://www.ibeta.com/iso-30107-3-presentation-attack-detection-confirmation-letters/#letters) compliance.
8686

8787
Tutorial
8888
- [Face liveness Tutorial](Tutorials/liveness.md)

‎articles/ai-services/computer-vision/tutorials/liveness.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -445,7 +445,7 @@ The high-level steps involved in liveness with verification orchestration are il
445445

446446
var sessionClient = new FaceSessionClient(endpoint, credential);
447447

448-
var createContent = new CreateLivenessSessionContent(LivenessOperationMode.Passive)
448+
var createContent = new CreateLivenessWithVerifySessionContent(LivenessOperationMode.Passive)
449449
{
450450
DeviceCorrelationId = "723d6d03-ef33-40a8-9682-23a1feb7bccd"
451451
};
@@ -472,7 +472,7 @@ The high-level steps involved in liveness with verification orchestration are il
472472
.credential(new AzureKeyCredential(accountKey))
473473
.buildClient();
474474

475-
CreateLivenessSessionContent parameters = new CreateLivenessSessionContent(LivenessOperationMode.PASSIVE)
475+
CreateLivenessWithVerifySessionContent parameters = new CreateLivenessWithVerifySessionContent(LivenessOperationMode.PASSIVE)
476476
.setDeviceCorrelationId("723d6d03-ef33-40a8-9682-23a1feb7bccd")
477477
.setSendResultsToClient(false);
478478

@@ -500,7 +500,7 @@ The high-level steps involved in liveness with verification orchestration are il
500500
reference_image_content = fd.read()
501501

502502
created_session = await face_session_client.create_liveness_with_verify_session(
503-
CreateLivenessSessionContent(
503+
CreateLivenessWithVerifySessionContent(
504504
liveness_operation_mode=LivenessOperationMode.PASSIVE,
505505
device_correlation_id="723d6d03-ef33-40a8-9682-23a1feb7bccd",
506506
),

‎articles/ai-services/content-safety/concepts/custom-categories.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ This implementation works on text content and image content.
4949

5050
## How it works
5151

52-
#### [Custom categories (standard) API](#tab/standard)
52+
### [Custom categories (standard) API](#tab/standard)
5353

5454
The Azure AI Content Safety custom categories feature uses a multi-step process for creating, training, and using custom content classification models. Here's a look at the workflow:
5555

‎articles/ai-services/content-safety/includes/storage-account-access.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,9 @@ ms.author: pafarley
1010
---
1111

1212

13-
Next, you need to give your Content Safety resource access to read from the Azure Storage resource. Enable system-assigned Managed identity for the Azure AI Content Safety instance and assign the role of **Storage Blob Data Contributor/Owner/Reader** to the identity:
13+
Next, you need to give your Content Safety resource access to read from the Azure Storage resource. Enable system-assigned Managed identity for the Azure AI Content Safety instance and assign the role of **Storage Blob Data Contributor/Owner** to the identity:
14+
> [!IMPORTANT]
15+
> **Only Storage Blob Data Contributor or Storage Blob Data Owner are valid roles to proceed.**
1416
1517
1. Enable managed identity for the Azure AI Content Safety instance.
1618

‎articles/ai-services/content-safety/overview.md

Lines changed: 35 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,15 @@ Currently, Azure AI Content Safety has an **F0** and **S0** pricing tier. See th
9999

100100
## Service limits
101101

102+
> [!CAUTION]
103+
> **Deprecation Notice**
104+
>
105+
> As part of Content Safety versioning and lifecycle management, we are announcing the deprecation of certain Public Preview and GA versions of our service APIs. Following our deprecation policy:
106+
> * **Public Preview versions**: Each new Public Preview version will trigger the deprecation of the previous preview version after a 90-day period, provided no breaking changes are introduced.
107+
> * **GA versions**: When a new GA version is released, the prior GA version will be deprecated after a 90-day period if compatibility is maintained.
108+
>
109+
> See the [What's new](./whats-new.md) page for upcoming deprecations.
110+
102111
### Input requirements
103112

104113
See the following list for the input requirements for each feature.
@@ -140,49 +149,32 @@ For more information, see [Language support](/azure/ai-services/content-safety/l
140149

141150
### Region availability
142151

143-
To use the Content Safety APIs, you must create your Azure AI Content Safety resource in a supported region. Currently, the Content Safety features are available in the following Azure regions:
144-
145-
| Region | Moderation APIs (text and image) | Moderation APIs (multimodal) (preview) | Prompt Shields | Protected material detection for Text | Protected material detection for Code | Groundedness detection (preview) | Custom categories (rapid) (preview) | Custom categories (standard) (preview) |
146-
|--|-|---|-|--|---|-|-|---|
147-
| Australia East | ✅ | | ✅ | ✅ | ✅ | | ✅ | ✅|
148-
| Brazil South | ✅ | | ✅| ✅ | | | | |
149-
| Canada Central |✅ | | ✅ |✅ | | | | |
150-
| Central India | | | ✅ | ✅ | | | | |
151-
| Canada East | ✅ | | ✅ | ✅ | ✅ | | ✅ | |
152-
| Central US | ✅ | | | ✅ | ✅ | | ✅ | |
153-
| East US | ✅ |✅| ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
154-
| East US 2 | ✅ | | ✅ | ✅ | ✅ | ✅| ✅ | |
155-
| France Central | ✅ | | ✅ | ✅ | ✅ | | ✅ | |
156-
| Germany West Central|✅| | ✅| ✅ | | | | |
157-
| India North | | |✅ |✅ | | | | |
158-
| Italy North | ✅ | | ✅| ✅ | | | | |
159-
| Japan East | ✅ | | ✅ | ✅ | ✅ | | ✅ | |
160-
| Japan West | | | | | ✅ | | ✅ | |
161-
| Korea Central | ✅ | | | | | | | |
162-
| North Central US | ✅ | | ✅ | ✅ | ✅ | | ✅ | |
163-
| Norway East |✅ | | | | | | | |
164-
| Poland Central | ✅ | | ✅ | ✅ | ✅ | | ✅ | |
165-
| South Africa North| ✅| | ✅ | ✅ | ✅ | | | |
166-
| South Central US | ✅ | | | | ✅ | | ✅ | |
167-
| South East Asia | | | ✅ | ✅ | | | ✅ | |
168-
| South India | ✅ | | | ✅ | ✅ | | ✅ | |
169-
| Sweden Central | ✅ | | ✅ | ✅ | ✅ | ✅| ✅ | |
170-
| Switzerland North | ✅ | | ✅ | ✅ | | | ✅ | ✅ |
171-
| Switzerland West | ✅ | | ✅ | ✅ | | | ✅ | ✅ |
172-
| UAE North | ✅ | | | | | | | |
173-
| UK South | ✅ | | ✅ | ✅ | | | ✅ | |
174-
| West Europe | ✅ |✅| ✅ | ✅ | ✅ | | ✅ | |
175-
| West US | | | ✅ | ✅ | ✅ | | ✅ | |
176-
| West US 2 | ✅ | | ✅ | ✅ | ✅ | | ✅ | |
177-
| West US 3 | ✅ | | ✅ | ✅ | ✅ | | ✅ | |
178-
| USGov Arizona | ✅ | | ✅ | ✅ | | | | |
179-
| USGov Virginia | ✅ | | ✅ | ✅ | | | | |
180-
181-
182-
183-
184-
185-
152+
To use the Content Safety APIs, you must create your Azure AI Content Safety resource in a supported region. Currently, the Content Safety features are available in the following Azure regions with different API versions:
153+
154+
| Region | Custom Category | Groundedness | Image | Multimodal(Image with Tex) | Incident Response | Prompt Shield | Protected Material (Text) | Protected Material (Code) | Text | Unified API |
155+
|--------------------|--------------------|--------------------|-------|-----------------|-------------------|---------------|---------------------------|---------------------------|------|-------------|
156+
| Australia East | ✅ | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
157+
| Canada East | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
158+
| Central US | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
159+
| East US | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
160+
| East US 2 | | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
161+
| France Central | | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
162+
| Japan East | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
163+
| North Central US | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
164+
| Poland Central | | | ✅ | | | ✅ | ✅ | ✅ | ✅ | ✅ |
165+
| South Central US | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
166+
| South India | | | ✅ | | ✅ | | ✅ | ✅ | ✅ | ✅ |
167+
| Sweden Central | | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
168+
| Switzerland North | ✅ | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
169+
| Switzerland West | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | |
170+
| UAE North | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | |
171+
| UK South | | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
172+
| West Europe | | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
173+
| West US | | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
174+
| West US 2 | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
175+
| West US 3 | | | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
176+
| FairFax - USGovArizona| | | ✅ | | | ✅ | ✅ | | ✅ | ✅ |
177+
| FairFax - USGovVirginia| | | ✅ | | | ✅ | ✅ | | ✅ | ✅ |
186178

187179
Feel free to [contact us](mailto:[email protected]) if your business needs other regions to be available.
188180

0 commit comments

Comments
 (0)