Skip to content

Commit 78c6d10

Browse files
committed
remove tab groups
1 parent 98746e2 commit 78c6d10

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

articles/container-apps/managed-identity.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -354,11 +354,7 @@ To get a token for a resource, make an HTTP `GET` request to the endpoint, inclu
354354

355355
Starting in API version `2024-02-02-preview`, you can use managed identities in your scale rules to authenticate with Azure services that support managed identities. To use a managed identity in your scale rule, use the `identity` property instead of the `auth` property in your scale rule. Acceptable values for the `identity` property are either the Azure resource ID of a user-assigned identity, or `system` to use a system-assigned identity
356356

357-
The following example shows how to use a managed identities with an Azure Queue Storage scale rule:
358-
359-
# [ARM template](#tab/arm)
360-
361-
The queue storage account uses the `accountName` property to identify the storage account, while the `identity` property specifies which managed identity to use. You do not need to use the `auth` property.
357+
The following example shows how to use a managed identities with an Azure Queue Storage scale rule. The queue storage account uses the `accountName` property to identify the storage account, while the `identity` property specifies which managed identity to use. You do not need to use the `auth` property.
362358

363359
```json
364360
"scale": {
@@ -395,8 +391,6 @@ The following example shows how to configure a container app on a workload profi
395391

396392
This approach limits the resources that can be accessed if a malicious actor were to gain unauthorized access to the containers.
397393

398-
# [ARM template](#tab/arm)
399-
400394
```json
401395
{
402396
"location": "eastus2",

0 commit comments

Comments
 (0)