Skip to content

Commit a924745

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us297322-content-curation
2 parents e7b582b + 5bd10ea commit a924745

File tree

47 files changed

+331
-120
lines changed

Some content is hidden

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

47 files changed

+331
-120
lines changed

.openpublishing.redirection.azure-app-configuration.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@
2727
},
2828
{
2929
"source_path_from_root": "/articles/azure-app-configuration/concept-github-action.md",
30-
"redirect_url": "/azure/azure-app-configuration/push-kv-github-action.md",
30+
"redirect_url": "/azure/azure-app-configuration/push-kv-github-action",
3131
"redirect_document_id": false
3232
}
3333
]

articles/ai-services/document-intelligence/concept-custom-neural.md

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -286,9 +286,12 @@ Starting with version `2024-07-31-preview`, you can train your custom neural mod
286286
You can choose to spend all of 10 free hours on a single model build with a large set of data, or utilize it across multiple builds by adjusting the maximum duration value for the `build` operation by specifying `maxTrainingHours`:
287287

288288
```bash
289+
POST https://{endpoint}/documentintelligence/documentModels:build?api-version=2024-07-31-preview
289290

290-
POST /documentModels:build
291291
{
292+
"modelId": "string",
293+
"description": "string",
294+
"buildMode": "neural",
292295
...,
293296
"maxTrainingHours": 10
294297
}
@@ -299,7 +302,7 @@ POST /documentModels:build
299302
> * If you would like to train additional neural models or train models for a longer time period that **exceed 10 hours**, billing charges apply. For details on the billing charges, refer to the [pricing page](https://azure.microsoft.com/pricing/details/ai-document-intelligence/).
300303
> * You can opt in for this paid training service by setting the `maxTrainingHours` to the desired maximum number of hours. API calls with no budget but with the `maxTrainingHours` set as over 10 hours will fail.
301304
> * As each build takes different amount of time depending on the type and size of the training dataset, billing is calculated for the actual time spent training the neural model, with a minimum of 30 minutes per training job.
302-
> * This paid billing structure enables you to train larger data sets for longer durations with flexibility in the training hours.
305+
> * This paid training feature enables you to train larger data sets for longer durations with flexibility in the training hours.
303306
304307
```bash
305308

@@ -321,7 +324,11 @@ GET /documentModels/{myCustomModel}
321324
322325
## Billing
323326
324-
For Document Intelligence versions `v3.1 (2023-07-31) and v3.0 (2022-08-31)`, you receive a maximum 30 minutes of training duration per model, and a maximum of 20 trainings for free per month. If you would like to train more than 20 model instances, you can create an [Azure support ticket](service-limits.md#create-and-submit-support-request) to increase in the training limit. For the Azure support ticket, enter in the `summary` section a phrase such as `Increase Document Intelligence custom neural training (TPS) limit`. A ticket can only apply at a resource-level, not a subscription level. You can request a training limit increase for a single Document Intelligence resource by specifying your resource ID and region in the support ticket.
327+
For Document Intelligence versions `v3.1 (2023-07-31) and v3.0 (2022-08-31)`, you receive a maximum 30 minutes of training duration per model, and a maximum of 20 trainings for free per month. If you would like to train more than 20 model instances, you can create an [Azure support ticket](service-limits.md#create-and-submit-support-request) to increase in the training limit. For Azure support ticket, enter in the `summary` field: `Increase Document Intelligence custom neural training (TPS) limit`.
328+
329+
> [!IMPORTANT]
330+
> * When increasing the training limit, note that 2 custom neural model training sessions will be considered as 1 training hour. For more details on the pricing for increasing the number of training sessions, refer to the [pricing page](https://azure.microsoft.com/pricing/details/ai-document-intelligence/).
331+
> * Azure support ticket for training limit increase can only apply at a **resource-level**, not a subscription level. You can request a training limit increase for a single Document Intelligence resource by specifying your resource ID and region in the support ticket.
325332
326333
If you want to train models for longer durations than 30 minutes, we support **paid training** with our newest version, `v4.0 (2024-07-31-preview)`. Using the latest version, you can train your model for a longer duration to process larger documents. For more information about paid training, *see* [Billing v4.0](service-limits.md#billing).
327334
@@ -331,7 +338,11 @@ If you want to train models for longer durations than 30 minutes, we support **p
331338
332339
## Billing
333340
334-
For Document Intelligence versions `v3.1 (2023-07-31) and v3.0 (2022-08-31)`, you receive a maximum 30 minutes of training duration per model, and a maximum of 20 trainings for free per month. If you would like to train more than 20 model instances, you can create an [Azure support ticket](service-limits.md#create-and-submit-support-request) to increase in the training limit. For the Azure support ticket, enter in the `summary` section a phrase such as `Increase Document Intelligence custom neural training (TPS) limit`. A ticket can only apply at a resource-level, not a subscription level. You can request a training limit increase for a single Document Intelligence resource by specifying your resource ID and region in the support ticket.
341+
For Document Intelligence versions `v3.1 (2023-07-31) and v3.0 (2022-08-31)`, you receive a maximum 30 minutes of training duration per model, and a maximum of 20 trainings for free per month. If you would like to train more than 20 model instances, you can create an [Azure support ticket](service-limits.md#create-and-submit-support-request) to increase in the training limit. For Azure support ticket, enter in the `summary` field: `Increase Document Intelligence custom neural training (TPS) limit`.
342+
343+
> [!IMPORTANT]
344+
> * When increasing the training limit, note that 2 custom neural model training sessions will be considered as 1 training hour. For more details on the pricing for increasing the number of training sessions, refer to the [pricing page](https://azure.microsoft.com/pricing/details/ai-document-intelligence/).
345+
> * Azure support ticket for training limit increase can only apply at a **resource-level**, not a subscription level. You can request a training limit increase for a single Document Intelligence resource by specifying your resource ID and region in the support ticket.
335346
336347
If you want to train models for longer durations than 30 minutes, we support **paid training** with our newest version, `v4.0 (2024-07-31)`. Using the latest version, you can train your model for a longer duration to process larger documents. For more information about paid training, *see* [Billing v4.0](service-limits.md#billing).
337348

articles/ai-services/document-intelligence/faq.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -291,15 +291,15 @@ sections:
291291
- question: |
292292
Am I charged when training a custom models?
293293
answer: |
294-
**Yes**
294+
**Yes.**
295295
296-
Although training is free for all custom generative and custom template models, creating the training dataset for all models requires running the Layout model on the training documents. Customers are responsible for this cost.
296+
Training is free for all custom generative and custom template models. However, creating the training dataset for all models requires running the Layout model on the training documents. Customers are responsible for this cost.
297297
298298
Custom generative models also rely on the auto label feature to speed up the generation of the labeled dataset. There's a cost associated with this action. While the build operation for template and generative models is free, creating the labeled dataset can result in some minimal costs.
299299
300-
Custom neural models have a limit on the number of models/the amount of time that models can be trained for free. The first 10 hours of training are free. If training a single model for longer than 10 hours or training multiple models that exceed the 10 hour limit, you need to enable paid training by setting a training budget. See [training a custom neural model](concept-custom-neural.md) for details.
300+
For `v4.0 2024-07-31-preview`, custom neural models can be trained for free for a **maximum of 10 hours**. Whether you are training a single model for the 10 hours, or training multiple models for the total of 10 hours, you won't be charged for the first 10 hours. After using up the free 10 hours, you will be **automatically charged by the extra training hour**. For details on the prices, refer to the [pricing page](https://azure.microsoft.com/pricing/details/ai-document-intelligence/). This new paid training feature enables training models for an extended duration to process larger documents. For more information on this paid training feature, check [custom neural model billing section](concept-custom-neural.md#billing).
301301
302-
For v3.0 or v3.1 models the paid training tier only applies to added models, the training time per model isn't configurable.
302+
For `v3.0 2022-08-31` or `v3.1 2023-07-31`, custom neural models can be trained for free for a maximum of 20 training sessions, with each session capped at 30 minutes of training duration. Once you use up all of the 20 training sessions, you can submit Azure support ticket to increase the training session limit. For increasing the limit, 2 training sessions will be considered as 1 training hour, and you will be charged per 2 sessions / 1 training hour. For details on the prices, refer to the [pricing page]. For more information on ways to increase the limit, check [custom neural model billing section](concept-custom-neural.md#billing). **Note that for `v3.0` and `v3.1`, paid training feature is unavailable. Paid training feature for custom neural model is only available on `v4.0`.**
303303
304304
- name: Storage account
305305
questions:

articles/api-management/api-management-howto-aad-b2c.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: engagement-fy23
1414

1515
# How to authorize developer accounts by using Azure Active Directory B2C in Azure API Management
1616

17-
[!INCLUDE [api-management-availability-premium-dev-standard-basic-standardv2-basicv2](../../includes/api-management-availability-premium-dev-standard-basic-standardv2-basicv2.md)]
17+
[!INCLUDE [premium-dev-standard-standardv2-basicv2.md](../../includes/api-management-availability-premium-dev-standard-standardv2-basicv2.md)]
1818

1919
Azure Active Directory B2C is a cloud identity management solution for consumer-facing web and mobile applications. You can use it to manage access to your API Management developer portal.
2020

articles/api-management/api-management-howto-aad.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.custom: engagement-fy23, devx-track-azurecli
1313

1414
# Authorize developer accounts by using Microsoft Entra ID in Azure API Management
1515

16+
[!INCLUDE [premium-dev-standard-standardv2-basicv2.md](../../includes/api-management-availability-premium-dev-standard-standardv2-basicv2.md)]
17+
18+
1619
In this article, you'll learn how to:
1720
> [!div class="checklist"]
1821
> * Enable access to the developer portal for users from Microsoft Entra ID.
@@ -33,8 +36,6 @@ For an overview of options to secure the developer portal, see [Secure access to
3336

3437
[!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
3538

36-
[!INCLUDE [premium-dev-standard.md](../../includes/api-management-availability-premium-dev-standard.md)]
37-
3839
[!INCLUDE [api-management-navigate-to-instance.md](../../includes/api-management-navigate-to-instance.md)]
3940

4041

articles/azure-arc/resource-bridge/network-requirements.md

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -19,16 +19,7 @@ Arc resource bridge communicates outbound securely to Azure Arc over TCP port 44
1919

2020
> [!NOTE]
2121
> The URLs listed here are required for Arc resource bridge only. Other Arc products (such as Arc-enabled VMware vSphere) may have additional required URLs. For details, see [Azure Arc network requirements](../network-requirements-consolidated.md#azure-arc-enabled-vmware-vsphere).
22-
23-
## Designated IPs used by Arc resource bridge
24-
25-
When Arc resource bridge is deployed, there are designated IPs used exclusively by the appliance VM for the Kubernetes pods and services. These IPs can only be used for Arc resource bridge and can’t be used by any other service. If another service already uses an IP address within these ranges, please submit a support ticket.
26-
27-
28-
| Service|Designated Arc resource bridge IPs|
29-
| -------- | -------- |
30-
|Arc resource bridge Kubernetes pods |10.244.0.0/16 |
31-
| Arc resource bridge Kubernetes services| 10.96.0.0/12 |
22+
>
3223
3324
## SSL proxy configuration
3425

articles/azure-monitor/agents/data-collection-log-text.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -132,35 +132,35 @@ Use the following ARM template to create or modify a DCR for collecting text log
132132
"type": "string",
133133
"metadata": {
134134
"description": "Unique name for the DCR. "
135-
},
135+
}
136136
},
137137
"location": {
138138
"type": "string",
139139
"metadata": {
140140
"description": "Region for the DCR. Must be the same location as the Log Analytics workspace. "
141-
},
141+
}
142142
},
143143
"filePatterns": {
144144
"type": "string",
145145
"metadata": {
146146
"description": "Path on the local disk for the log file to collect. May include wildcards.Enter multiple file patterns separated by commas (AMA version 1.26 or higher required for multiple file patterns on Linux)."
147-
},
147+
}
148148
},
149149
"tableName": {
150150
"type": "string",
151151
"metadata": {
152152
"description": "Name of destination table in your Log Analytics workspace. "
153-
},
153+
}
154154
},
155155
"workspaceResourceId": {
156156
"type": "string",
157157
"metadata": {
158158
"description": "Resource ID of the Log Analytics workspace with the target table."
159-
},
159+
}
160160
}
161161
},
162162
"variables": {
163-
"tableOutputStream": "['Custom-',concat(parameters('tableName'))]"
163+
"tableOutputStream": "[concat('Custom-', parameters('tableName'))]"
164164
},
165165
"resources": [
166166
{

articles/batch/quick-create-portal.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
title: 'Quickstart: Use the Azure portal to create a Batch account and run a job'
33
description: Follow this quickstart to use the Azure portal to create a Batch account, a pool of compute nodes, and a job that runs basic tasks on the pool.
4-
ms.date: 06/13/2024
4+
ms.date: 07/30/2024
5+
ms.service: azure-batch
56
ms.topic: quickstart
67
ms.custom: mvc, mode-ui
78
---

articles/cdn/migrate-tier.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Migrate Azure CDN from Microsoft (classic) to Azure Front Door Standard or Premium tier (preview)
2+
title: Migrate Azure CDN from Microsoft (classic) to Azure Front Door Standard or Premium tier
33
description: This article provides step-by-step instructions on how to migrate from an Azure CDN from Microsoft (classic) profile to an Azure Front Door Standard or Premium tier profile.
44
services: cdn
55
author: duongau
@@ -9,11 +9,7 @@ ms.date: 06/25/2024
99
ms.author: duau
1010
---
1111

12-
# Migrate Azure CDN from Microsoft (classic) to Standard/Premium tier (preview)
13-
14-
> [!IMPORTANT]
15-
> Azure CDN from Microsoft to Azure Front Door migration is currently in PREVIEW.
16-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
12+
# Migrate Azure CDN from Microsoft (classic) to Standard/Premium tier
1713

1814
Azure Front Door Standard and Premium tier bring the latest cloud delivery network features to Azure. With enhanced security features and an all-in-one service, your application content is secured and closer to your end users using the Microsoft global network. This article guides you through the migration process to move your Azure CDN from Microsoft (classic) profile to either a Standard or Premium tier profile.
1915

12.9 KB
Loading

0 commit comments

Comments
 (0)