Skip to content

Commit fa2318b

Browse files
committed
resolve conflict
2 parents e4efceb + 9b6d76c commit fa2318b

File tree

634 files changed

+9359
-5847
lines changed

Some content is hidden

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

634 files changed

+9359
-5847
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33690,6 +33690,6 @@
3369033690
"source_path_from_root": "/articles/active-directory-domain-services/contact-us.md",
3369133691
"redirect_url": "/azure/active-directory/fundamentals/support-help-options",
3369233692
"redirect_document_id": false
33693-
},
33693+
}
3369433694
]
33695-
}
33695+
}

.openpublishing.redirection.azure-datalake-storage-gen1.json

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -289,16 +289,6 @@
289289
"source_path": "articles/data-lake-store/security-controls-policy.md",
290290
"redirect_url": "/previous-versions/azure/data-lake-store/security-controls-policy",
291291
"redirect_document_id": false
292-
},
293-
{
294-
"source_path": "articles/storage/blobs/data-lake-storage-migrate-gen1-to-gen2.md",
295-
"redirect_url": "/previous-versions/azure/storage/blobs/data-lake-storage-migrate-gen1-to-gen2",
296-
"redirect_document_id": false
297-
},
298-
{
299-
"source_path": "articles/storage/blobs/data-lake-storage-migrate-gen1-to-gen2-azure-portal.md",
300-
"redirect_url": "/previous-versions/azure/storage/blobs/data-lake-storage-migrate-gen1-to-gen2-azure-portal",
301-
"redirect_document_id": false
302292
}
303293

304294
]

.openpublishing.redirection.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6705,6 +6705,21 @@
67056705
"redirect_url": "/azure/active-directory/conditional-access/concept-conditional-access-cloud-apps",
67066706
"redirect_document_id": true
67076707
},
6708+
{
6709+
"source_path_from_root": "/articles/role-based-access-control/deny-assignments-portal.md",
6710+
"redirect_url": "/azure/role-based-access-control/deny-assignments",
6711+
"redirect_document_id": true
6712+
},
6713+
{
6714+
"source_path_from_root": "/articles/role-based-access-control/deny-assignments-powershell.md",
6715+
"redirect_url": "/azure/role-based-access-control/deny-assignments",
6716+
"redirect_document_id": false
6717+
},
6718+
{
6719+
"source_path_from_root": "/articles/role-based-access-control/deny-assignments-rest.md",
6720+
"redirect_url": "/azure/role-based-access-control/deny-assignments",
6721+
"redirect_document_id": false
6722+
},
67086723
{
67096724
"source_path_from_root": "/articles/scheduler/scheduler-intro.md",
67106725
"redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
@@ -10940,6 +10955,11 @@
1094010955
"redirect_url": "/azure/azure-health-insights/overview",
1094110956
"redirect_document_id": false
1094210957
},
10958+
{
10959+
"source_path_from_root": "/articles/azure-functions/functions-monitor-log-analytics.md",
10960+
"redirect_url": "/azure/azure-functions/monitor-functions",
10961+
"redirect_document_id": false
10962+
},
1094310963
{
1094410964
"source_path_from_root": "/articles/cloud-services-php-create-web-role.md",
1094510965
"redirect_url": "/azure/cloud-services/cloud-services-php-create-web-role",
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
{
2+
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/kubernetes-fleet/architectural-overview.md",
5+
"redirect_url": "/azure/kubernetes-fleet/concepts-fleet",
6+
"redirect_document_id": true
7+
}
8+
]
9+
}

.openpublishing.redirection.sql-database.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2580,6 +2580,6 @@
25802580
"source_path_from_root": "/articles/sql-data-warehouse/sql-data-warehouse-security-threat-detection.md",
25812581
"redirect_url": "/azure/sql-database/sql-database-threat-detection-overview",
25822582
"redirect_document_id": false
2583-
},
2583+
}
25842584
]
25852585
}

articles/advisor/advisor-reference-cost-recommendations.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ Learn more about [Log Analytics workspace - DeleteRestoredTables (Consider remov
136136

137137
### Consider enabling autopause on Spark compute
138138

139-
Auto-pause releases and shuts down unused Compute resources after a set idle period of inactivity.
139+
Autopause releases and shuts down unused Compute resources after a set idle period of inactivity.
140140

141141
Learn more about [Synapse workspace - EnableSynapseSparkComputeAutoPauseGuidance (Consider enabling autopause feature on spark compute.)](https://aka.ms/EnableSynapseSparkComputeAutoPauseGuidance).
142142

@@ -154,15 +154,15 @@ Learn more about [Synapse workspace - EnableSynapseSparkComputeAutoScaleGuidance
154154

155155
Customers running high IO workloads in Standard HDDs can upgrade to Standard SSDs and benefit from better performance and SLA and now experience a limit on the maximum number of billed transactions.
156156

157-
Learn more about [Disk - UpgradeHDDtoSDD (Standard SSD disks billing caps.)]().
157+
Learn more about [Understand Azure Disk Storage billing](/azure/virtual-machines/disks-understand-billing).
158158

159159
### Underutilized Disks Identified
160160

161161
You have disks that are utilized less than 10%, right-size to save cost.
162162

163-
Learn more about [Disk - wiprounderutilizeddisks (Underutilized Disks Identified)]().
163+
Learn more about [Managed disks: Find and delete unattached disks](/azure/virtual-machines/disks-find-unattached-portal).
164164

165-
### You have disks that have not been attached to a VM for more than 30 days. Evaluate if you still need the disk.
165+
### You have disks that haven't been attached to a VM for more than 30 days. Evaluate if you still need the disk.
166166

167167
We've observed that you have disks that haven't been attached to a VM for more than 30 days. Evaluate if you still need the disk. If you decide to delete the disk, recovery isn't possible. We recommend that you create a snapshot before deletion or ensure the data in the disk is no longer required.
168168

@@ -176,7 +176,7 @@ Learn more about [Virtual machine scale set - LowUsageVmss (Right-size or shutdo
176176

177177
### Use Virtual Machines with Ephemeral OS Disk enabled to save cost and get better performance
178178

179-
With Ephemeral OS Disk, You get these benefits: Save on storage cost for OS disk. Get lower read/write latency to OS disk. Faster VM Reimage operation by resetting OS (and Temporary disk) to its original state. It is preferable to use Ephemeral OS Disk for short-lived IaaS VMs or VMs with stateless workloads.
179+
With Ephemeral OS Disk, You get these benefits: Save on storage cost for OS disk. Get lower read/write latency to OS disk. Faster VM Reimage operation by resetting OS (and Temporary disk) to its original state. It's preferable to use Ephemeral OS Disk for short-lived IaaS VMs or VMs with stateless workloads.
180180

181181
Learn more about [Subscription - EphemeralOsDisk (Use Virtual Machines with Ephemeral OS Disk enabled to save cost and get better performance)](/azure/virtual-machines/windows/ephemeral-os-disks).
182182

@@ -205,7 +205,7 @@ Learn more about [PostgreSQL server - OrcasPostgreSqlCpuRightSize (Right-size un
205205

206206
### Review the configuration of your Azure Cosmos DB free tier account
207207

208-
Your Azure Cosmos DB free tier account currently contains resources with a total provisioned throughput exceeding 1000 Request Units per second (RU/s). Because the free tier only covers the first 1000 RU/s of throughput provisioned across your account, any throughput beyond 1000 RU/s is billed at the regular pricing. As a result, we anticipate that you're charged for the throughput currently provisioned on your Azure Cosmos DB account.
208+
Your Azure Cosmos DB free tier account currently contains resources with a total provisioned throughput exceeding 1,000 Request Units per second (RU/s). Because the free tier only covers the first 1000 RU/s of throughput provisioned across your account, any throughput beyond 1000 RU/s is billed at the regular pricing. As a result, we anticipate that you're charged for the throughput currently provisioned on your Azure Cosmos DB account.
209209

210210
Learn more about [Azure Cosmos DB account - CosmosDBFreeTierOverage (Review the configuration of your Azure Cosmos DB free tier account)](../cosmos-db/understand-your-bill.md#azure-free-tier).
211211

@@ -256,13 +256,13 @@ Learn more about [ExpressRoute circuit - ExpressRouteCircuit (Delete ExpressRout
256256

257257
### Repurpose or delete idle virtual network gateways
258258

259-
We noticed that your virtual network gateway has been idle for over 90 days. This gateway is being billed hourly. Reconfigure this gateway, or delete it if you do not intend to use it anymore.
259+
We noticed that your virtual network gateway has been idle for over 90 days. This gateway is being billed hourly. Reconfigure this gateway, or delete it if you don't intend to use it anymore.
260260

261261
Learn more about [Virtual network gateway - IdleVNetGateway (Repurpose or delete idle virtual network gateways)](https://aka.ms/aa_idlevpngateway_learnmore).
262262

263263
### Consider migrating to Front Door Standard/Premium
264264

265-
Your Front Door Classic tier contains a large number of domains or routing rules, which adds extra charges. Front Door Standard or Premium do not charge per additional domain or routing rule. Consider migrating to save costs.
265+
Your Front Door Classic tier contains a large number of domains or routing rules, which adds extra charges. Front Door Standard or Premium tiers don't charge per additional domain or routing rule. Consider migrating to save costs.
266266

267267
Learn more about [Front Door pricing](https://aka.ms/afd-pricing).
268268

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
- name: Azure
2+
tocHref: /azure/
3+
topicHref: /azure/index
4+
items:
5+
- name: Azure AI services
6+
tocHref: /azure/ai-services/
7+
topicHref: /azure/ai-services/index

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,25 +9,25 @@ manager: nitinme
99
ms.service: azure-ai-vision
1010
ms.subservice: azure-ai-face
1111
ms.topic: how-to
12-
ms.date: 05/11/2023
12+
ms.date: 03/07/2024
1313
ms.author: pafarley
1414
---
1515

1616
# Use limited access tokens for Face
1717

18-
Independent software vendors (ISVs) can manage the Face API usage of their clients by issuing access tokens that grant access to Face features which are normally gated. This allows client companies to use the Face API without having to go through the formal approval process.
18+
Independent software vendors (ISVs) can manage the Face API usage of their clients by issuing access tokens that grant access to Face features which are normally gated. This allows their client companies to use the Face API without having to go through the formal approval process.
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 LimitedAccessToken feature is a part of the existing [Azure AI services token service](https://westus.dev.cognitive.microsoft.com/docs/services/57346a70b4769d2694911369/operations/issueScopedToken). 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](https://westus.dev.cognitive.microsoft.com/docs/services/57346a70b4769d2694911369/operations/issueScopedToken). 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.
2323

2424
## Example use case
2525

26-
A company sells software that uses the Azure AI Face service to operate door access security systems. Their clients, individual manufacturers of door devices, subscribe to the software and run it on their devices. These client companies want to make Face API calls from their devices to perform Limited Access operations like face identification. By relying on access tokens from the ISV, they can bypass the formal approval process for face identification. The ISV, which has already been approved, can grant the client just-in-time access tokens.
26+
An example company sells software that uses the Azure AI Face service to operate door access security systems. Their clients, individual manufacturers of door devices, subscribe to the software and run it on their devices. These client companies want to make Face API calls from their devices to perform Limited Access operations like face identification. By relying on access tokens from the ISV, they can bypass the formal approval process for face identification. The ISV, which has already been approved, can grant the client just-in-time access tokens.
2727

2828
## Expectation of responsibility
2929

30-
The issuing ISV is responsible for ensuring that the tokens are used only for the approved purpose.
30+
The token-issuing ISV is responsible for ensuring that the tokens are used only for the approved purpose.
3131

3232
If the ISV learns that a client is using the LimitedAccessToken for non-approved purposes, the ISV should stop generating tokens for that customer. Microsoft can track the issuance and usage of LimitedAccessTokens, and we reserve the right to revoke an ISV's access to the **issueLimitedAccessToken** API if abuse is not addressed.
3333

@@ -80,7 +80,7 @@ The API should return a `200` response with the token in the form of a JSON web
8080

8181
## Step 3: Client application uses the token
8282

83-
The ISV's application can then pass the LimitedAccessToken as an HTTP request header for future Face API requests on behalf of the client. This works independently of other authentication mechanisms, so no personal information of the client's is ever leaked to the ISV.
83+
The ISV's application can then pass the limited access token as an HTTP request header for future Face API requests on behalf of the client. This works independently of other authentication mechanisms, so no personal information of the client's is ever leaked to the ISV.
8484

8585
> [!CAUTION]
8686
> The client doesn't need to be aware of the token value, as it can be passed in the background. If the client were to use a web monitoring tool to intercept the traffic, they'd be able to view the LimitedAccessToken header. However, because the token expires after a short period of time, they are limited in what they can do with it. This risk is known and considered acceptable.

articles/ai-services/content-safety/concepts/response-codes.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: nitinme
88
ms.service: azure-ai-content-safety
99
ms.custom: build-2023
1010
ms.topic: conceptual
11-
ms.date: 05/09/2023
11+
ms.date: 03/07/2024
1212
ms.author: pafarley
1313
---
1414

@@ -18,9 +18,9 @@ The content APIs may return the following error codes:
1818

1919
| Error Code | Possible reasons | Suggestions |
2020
| ---------- | ------- | -------------------- |
21-
| InvalidRequestBody | One or more fields in the request body do not match the API definition. | 1. Check the API version you specified in the API call. <br/>2. Check the corresponding API definition for the API version you selected. |
22-
| InvalidResourceName | The resource name you specified in the URL does not meet the requirements, like the blocklist name, blocklist term ID, etc. | 1. Check the API version you specified in the API call. <br/>2. Check whether the given name has invalid characters according to the API definition. |
23-
| ResourceNotFound | The resource you specified in the URL may not exist, like the blocklist name. | 1. Check the API version you specified in the API call. <br/> 2. Double check the existence of the resource specified in the URL. |
24-
| InternalError | Some unexpected situations on the server side have been triggered. | 1. You may want to retry a few times after a small period and see it the issue happens again. <br/> 2. Contact Azure Support if this issue persists. |
25-
| ServerBusy | The server side cannot process the request temporarily. | 1. You may want to retry a few times after a small period and see it the issue happens again. <br/>2.Contact Azure Support if this issue persists. |
26-
| TooManyRequests | The current RPS has exceeded the quota for your current SKU. | 1. Check the pricing table to understand the RPS quota. <br/>2.Contact Azure Support if you need more QPS. |
21+
| InvalidRequestBody | One or more fields in the request body do not match the API definition. | Check the API version you specified in the API call. <br/>Check the corresponding API definition for the API version you selected. |
22+
| InvalidResourceName | The resource name you specified in the URL does not meet the requirements, like the blocklist name, blocklist term ID, etc. | Check the API version you specified in the API call. <br/>Check whether the given name has invalid characters according to the API definition. |
23+
| ResourceNotFound | The resource you specified in the URL may not exist, like the blocklist name. | Check the API version you specified in the API call. <br/>Double check the existence of the resource specified in the URL. |
24+
| InternalError | Some unexpected situations on the server side have been triggered. | You may want to retry a few times after a small period and see it the issue happens again. <br/> Contact Azure Support if this issue persists. |
25+
| ServerBusy | The server side cannot process the request temporarily. | You may want to retry a few times after a small period and see it the issue happens again. <br/>Contact Azure Support if this issue persists. |
26+
| TooManyRequests | The current RPS has exceeded the quota for your current SKU. | Check the pricing table to understand the RPS quota. <br/>Contact Azure Support if you need more QPS. |

articles/ai-services/content-safety/how-to/use-blocklist.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The default AI classifiers are sufficient for most content moderation needs. How
2323
## Prerequisites
2424

2525
* An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services/)
26-
* Once you have your Azure subscription, <a href="https://aka.ms/acs-create" title="Create a Content Safety resource" target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select the subscription you entered on the application form, and select a resource group, supported region, and supported pricing tier. Then select **Create**.
26+
* Once you have your Azure subscription, <a href="https://aka.ms/acs-create" title="Create a Content Safety resource" target="_blank">create a Content Safety resource </a> in the Azure portal to get your key and endpoint. Enter a unique name for your resource, select your subscription, and select a resource group, supported region (East US or West Europe), and supported pricing tier. Then select **Create**.
2727
* The resource takes a few minutes to deploy. After it finishes, Select **go to resource**. In the left pane, under **Resource Management**, select **Subscription Key and Endpoint**. The endpoint and either of the keys are used to call APIs.
2828
* One of the following installed:
2929
* [cURL](https://curl.haxx.se/) for REST API calls.

0 commit comments

Comments
 (0)