Skip to content

Commit 25aef72

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into asergaz-aio-preview-fix
2 parents 31a603a + 2348ab6 commit 25aef72

File tree

1,098 files changed

+12496
-10913
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,098 files changed

+12496
-10913
lines changed

.openpublishing.redirection.app-service.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2659,6 +2659,21 @@
26592659
"source_path": "articles/app-service/quickstart-dotnet-framework.md",
26602660
"redirect_url": "/azure/app-service/quickstart-dotnetcore?tabs=netframework48",
26612661
"redirect_document_id": false
2662+
},
2663+
{
2664+
"source_path": "articles/app-service/quickstart-arm-template-uiex.md",
2665+
"redirect_url": "/azure/app-service/quickstart-arm-template",
2666+
"redirect_document_id": true
2667+
},
2668+
{
2669+
"source_path": "articles/app-service/quickstart-dotnetcore-uiex.md",
2670+
"redirect_url": "/azure/app-service/quickstart-dotnetcore",
2671+
"redirect_document_id": true
2672+
},
2673+
{
2674+
"source_path": "articles/app-service/quickstart-java-uiex.md",
2675+
"redirect_url": "/azure/app-service/quickstart-java",
2676+
"redirect_document_id": true
26622677
}
26632678
]
26642679
}

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6750,6 +6750,11 @@
67506750
"redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
67516751
"redirect_document_id": false
67526752
},
6753+
{
6754+
"source_path_from_root": "/articles/search/cognitive-search-tutorial-blob-python.md",
6755+
"redirect_url": "/azure/search/samples-python",
6756+
"redirect_document_id": false
6757+
},
67536758
{
67546759
"source_path_from_root": "/articles/search/semantic-ranking.md",
67556760
"redirect_url": "/azure/search/semantic-search-overview",

.openpublishing.redirection.sentinel.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1055,6 +1055,21 @@
10551055
"redirect_url": "/azure/sentinel/normalization-schema-process-event",
10561056
"redirect_document_id": true
10571057
},
1058+
{
1059+
"source_path_from_root": "/articles/sentinel/connect-cef-ama.md",
1060+
"redirect_url": "/azure/sentinel/connect-cef-syslog-ama",
1061+
"redirect_document_id": false
1062+
},
1063+
{
1064+
"source_path_from_root": "/articles/sentinel/connect-cef-syslog.md",
1065+
"redirect_url": "/azure/sentinel/connect-cef-syslog-ama",
1066+
"redirect_document_id": false
1067+
},
1068+
{
1069+
"source_path_from_root": "/articles/sentinel/connect-cef-syslog-options.md",
1070+
"redirect_url": "/azure/sentinel/connect-cef-syslog-ama",
1071+
"redirect_document_id": false
1072+
},
10581073
{
10591074
"source_path_from_root": "/articles/sentinel/notebooks-with-synapse.md",
10601075
"redirect_url": "/azure/sentinel/notebooks-hunt",

.whatsnew/.azure-monitor.json

Lines changed: 0 additions & 77 deletions
This file was deleted.

.whatsnew/.defender-for-iot.json

Lines changed: 0 additions & 23 deletions
This file was deleted.

.whatsnew/.security-center.json

Lines changed: 0 additions & 23 deletions
This file was deleted.

.whatsnew/.sentinel.json

Lines changed: 0 additions & 23 deletions
This file was deleted.

articles/ai-services/.openpublishing.redirection.ai-services-from-applied.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -635,7 +635,13 @@
635635
"source_path_from_root": "/articles/ai-services/translator/document-translation/quickstarts/document-translation-rest-api.md",
636636
"redirect_url": "/azure/ai-services/translator/document-translation/quickstarts/asynchronous-rest-api",
637637
"redirect_document_id": true
638+
},
639+
{
640+
"source_path_from_root": "/articles/ai-services/document-intelligence/concept-retrieval-augumented-generation.md",
641+
"redirect_url": "/azure/ai-services/document-intelligence/concept-retrieval-augmented-generation",
642+
"redirect_document_id": true
638643
}
639644

645+
640646
]
641647
}

articles/ai-services/cognitive-services-virtual-networks.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,7 @@ Virtual networks are supported in [regions where Azure AI services are available
5959
> - `AzureResourceManager`
6060
> - `CognitiveServicesManagement`
6161
> - `CognitiveServicesFrontEnd`
62+
> - `Storage` (Speech Studio only)
6263
6364
## Change the default network access rule
6465

articles/ai-services/computer-vision/Tutorials/liveness.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Face Liveness detection can be used to determine if a face in an input video str
1616

1717
The goal of liveness detection is to ensure that the system is interacting with a physically present live person at the time of authentication. Such systems have become increasingly important with the rise of digital finance, remote access control, and online identity verification processes.
1818

19-
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.
19+
The liveness detection solution successfully defends against various 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.
2020

2121
[!INCLUDE [liveness-sdk-gate](../includes/liveness-sdk-gate.md)]
2222

@@ -40,7 +40,7 @@ Once you have access to the SDK, follow instruction in the [azure-ai-vision-sdk]
4040
- For Swift iOS, follow the instructions in the [iOS sample](https://aka.ms/azure-ai-vision-face-liveness-client-sdk-ios-readme)
4141
- For Kotlin/Java Android, follow the instructions in the [Android sample](https://aka.ms/liveness-sample-java)
4242

43-
Once you've added the code into your application, the SDK will handle starting the camera, guiding the end-user to adjust their position, composing the liveness payload, and calling the Azure AI Face cloud service to process the liveness payload.
43+
Once you've added the code into your application, the SDK handles starting the camera, guiding the end-user to adjust their position, composing the liveness payload, and calling the Azure AI Face cloud service to process the liveness payload.
4444

4545
### Orchestrate the liveness solution
4646

@@ -86,7 +86,7 @@ The high-level steps involved in liveness orchestration are illustrated below:
8686

8787
1. The SDK then starts the camera, guides the user to position correctly and then prepares the payload to call the liveness detection service endpoint.
8888

89-
1. The SDK calls the Azure AI Vision Face service to perform the liveness detection. Once the service responds, the SDK will notify the mobile application that the liveness check has been completed.
89+
1. The SDK calls the Azure AI Vision Face service to perform the liveness detection. Once the service responds, the SDK notifies the mobile application that the liveness check has been completed.
9090

9191
1. The mobile application relays the liveness check completion to the app server.
9292

@@ -110,7 +110,7 @@ The high-level steps involved in liveness orchestration are illustrated below:
110110
"method": "POST",
111111
"contentLength": 352568,
112112
"contentType": "multipart/form-data; boundary=--------------------------482763481579020783621915",
113-
"userAgent": "PostmanRuntime/7.34.0"
113+
"userAgent": ""
114114
},
115115
"response": {
116116
"body": {
@@ -162,12 +162,12 @@ Use the following tips to ensure that your input images give the most accurate r
162162
#### Composition requirements:
163163
- Photo is clear and sharp, not blurry, pixelated, distorted, or damaged.
164164
- Photo is not altered to remove face blemishes or face appearance.
165-
- Photo must be in an RGB color supported format (JPEG, PNG, WEBP, BMP). Recommended Face size is 200 pixels x 200 pixels. Face sizes larger than 200 pixels x 200 pixels will not result in better AI quality, and no larger than 6MB in size.
165+
- Photo must be in an RGB color supported format (JPEG, PNG, WEBP, BMP). Recommended Face size is 200 pixels x 200 pixels. Face sizes larger than 200 pixels x 200 pixels will not result in better AI quality, and no larger than 6 MB in size.
166166
- User is not wearing glasses, masks, hats, headphones, head coverings, or face coverings. Face should be free of any obstructions.
167167
- Facial jewelry is allowed provided they do not hide your face.
168168
- Only one face should be visible in the photo.
169169
- Face should be in neutral front-facing pose with both eyes open, mouth closed, with no extreme facial expressions or head tilt.
170-
- Face should be free of any shadows or red eyes. Please retake photo if either of these occur.
170+
- Face should be free of any shadows or red eyes. Retake photo if either of these occur.
171171
- Background should be uniform and plain, free of any shadows.
172172
- Face should be centered within the image and fill at least 50% of the image.
173173

@@ -243,7 +243,7 @@ The high-level steps involved in liveness with verification orchestration are il
243243
"method": "POST",
244244
"contentLength": 352568,
245245
"contentType": "multipart/form-data; boundary=--------------------------590588908656854647226496",
246-
"userAgent": "PostmanRuntime/7.34.0"
246+
"userAgent": ""
247247
},
248248
"response": {
249249
"body": {

0 commit comments

Comments
 (0)