Skip to content

Commit 540425d

Browse files
authored
Merge pull request #287207 from MicrosoftDocs/main
9/23/2024 PM Publish
2 parents 3d09e4e + b804be9 commit 540425d

File tree

85 files changed

+599
-275
lines changed

Some content is hidden

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

85 files changed

+599
-275
lines changed

.openpublishing.redirection.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2597,7 +2597,7 @@
25972597
},
25982598
{
25992599
"source_path": "articles/managed-grafana/how-to-sync-teams-with-azure-ad-groups.md",
2600-
"redirect_url": "managed-grafana/how-to-sync-teams-with-entra-groups",
2600+
"redirect_url": "how-to-sync-teams-with-entra-groups",
26012601
"redirect_document_id": false
26022602
},
26032603
{

articles/app-service/environment/overview.md

Lines changed: 91 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ A benefit of using an App Service Environment instead of a multitenant service i
6969
App Service Environment v3 differs from earlier versions in the following ways:
7070

7171
- There are no networking dependencies on the customer's virtual network. You can secure all inbound and outbound traffic and route outbound traffic as you want.
72-
- You can deploy an App Service Environment v3 that's enabled for zone redundancy. You set zone redundancy only during creation and only in regions where all App Service Environment v3 dependencies are zone redundant. In this case, each App Service Plan on the App Service Environment will need to have a minimum of three instances so that they can be spread across zones. For more information, see [Migrate App Service Environment to availability zone support](../../availability-zones/migrate-app-service-environment.md).
72+
- You can deploy an App Service Environment v3 that's enabled for zone redundancy. You set zone redundancy only during creation and only in regions where all App Service Environment v3 dependencies are zone redundant. This is a deployment time only decision. Changing zone redundancy is not possible after it has been deployed. With zone redundant App Service Environment, each App Service Plan on the App Service Environment will need to have a minimum of three instances so that they can be spread across zones. For more information, see [Migrate App Service Environment to availability zone support](../../availability-zones/migrate-app-service-environment.md).
7373
- You can deploy an App Service Environment v3 on a dedicated host group. Host group deployments aren't zone redundant.
7474
- Scaling is much faster than with an App Service Environment v2. Although scaling still isn't immediate, as in the multitenant service, it's a lot faster.
7575
- Front-end scaling adjustments are no longer required. App Service Environment v3 front ends automatically scale to meet your needs and are deployed on better hosts.
@@ -165,6 +165,7 @@ App Service Environment v3 is available in the following regions:
165165
| Southeast Asia |||
166166
| Spain Central ||** |
167167
| Sweden Central |||
168+
| Sweden South || |
168169
| Switzerland North |||
169170
| Switzerland West || |
170171
| UAE Central || |
@@ -188,23 +189,109 @@ App Service Environment v3 is available in the following regions:
188189
| US DoD Central || |
189190
| US DoD East || |
190191
| US Gov Arizona || |
191-
| US Gov Iowa | | |
192192
| US Gov Texas || |
193193
| US Gov Virginia |||
194194

195195
### Microsoft Azure operated by 21Vianet
196196

197197
| Region | Single zone support | Availability zone support |
198198
| -------------------- | :--------------------------: | :-------------------------: |
199-
| China East 2 | | |
199+
| | App Service Environment v3 | App Service Environment v3 |
200200
| China East 3 || |
201-
| China North 2 | | |
202201
| China North 3 |||
203202

204203
### In-region data residency
205204

206205
An App Service Environment will only store customer data including app content, settings and secrets within the region where it's deployed. All data is guaranteed to remain in the region. For more information, see [Data residency in Azure](https://azure.microsoft.com/explore/global-infrastructure/data-residency/#overview).
207206

207+
## Pricing tiers
208+
209+
The following sections list the regional pricing tiers (SKUs) availability for App Service Environment v3.
210+
211+
> [!NOTE]
212+
> Windows Container plans currently do not support memory intensive SKUs.
213+
>
214+
215+
### Azure Public:
216+
217+
| Region | Standard | Large | Memory intensive |
218+
| -------------------- | :----------: | :---------: | :---------------: |
219+
| | I1v2-I3v2 | I4v2-I6v2 | I1mv2-I5mv2 |
220+
| Australia Central ||||
221+
| Australia Central 2 ||||
222+
| Australia East ||||
223+
| Australia Southeast ||||
224+
| Brazil South ||| |
225+
| Brazil Southeast ||||
226+
| Canada Central ||||
227+
| Canada East ||||
228+
| Central India ||||
229+
| Central US || ✅ * | |
230+
| East Asia ||||
231+
| East US ||| |
232+
| East US 2 ||||
233+
| France Central ||||
234+
| France South ||||
235+
| Germany North ||||
236+
| Germany West Central ||||
237+
| Israel Central ||| |
238+
| Italy North ||| |
239+
| Japan East ||||
240+
| Japan West ||||
241+
| Jio India Central ||| |
242+
| Jio India West ||| |
243+
| Korea Central ||| |
244+
| Korea South ||||
245+
| Mexico Central ||| |
246+
| North Central US ||||
247+
| North Europe ||||
248+
| Norway East ||||
249+
| Norway West ||||
250+
| Poland Central ||| |
251+
| Qatar Central ||| |
252+
| South Africa North ||||
253+
| South Africa West ||||
254+
| South Central US ||||
255+
| South India ||| |
256+
| Southeast Asia ||||
257+
| Spain Central ||| |
258+
| Sweden Central ||||
259+
| Sweden South ||||
260+
| Switzerland North ||||
261+
| Switzerland West ||||
262+
| UAE Central ||| |
263+
| UAE North ||||
264+
| UK South ||||
265+
| UK West ||||
266+
| West Central US || ✅ * | |
267+
| West Europe || ✅ * | |
268+
| West India ||||
269+
| West US ||| |
270+
| West US 2 ||||
271+
| West US 3 ||||
272+
273+
\* Windows Container does not support Large skus in this region.
274+
\** Linux does not support Memory intensive skus in this region.
275+
276+
### Azure Government:
277+
278+
| Region | Standard | Large | Memory intensive |
279+
| -------------------- | :----------: | :---------: | :---------------: |
280+
| | I1v2-I3v2 | I4v2-I6v2 | I1mv2-I5mv2 |
281+
| US DoD Central ||✅ * | |
282+
| US DoD East ||✅ * | |
283+
| US Gov Arizona ||✅ * | |
284+
| US Gov Texas ||✅ * | |
285+
| US Gov Virginia ||✅ * | |
286+
287+
### Microsoft Azure operated by 21Vianet:
288+
289+
| Region | Standard | Large | Memory intensive |
290+
| -------------------- | :----------: | :---------: | :---------------: |
291+
| | I1v2-I3v2 | I4v2-I6v2 | I1mv2-I5mv2 |
292+
| China East 3 || ✅ * | |
293+
| China North 3 || ✅ * | |
294+
208295
## Next steps
209296

210297
> [!div class="nextstepaction"]

articles/azure-resource-manager/managed-applications/approve-just-in-time-access.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
title: Approve just-in-time access
33
description: Describes how consumers of Azure Managed Applications approve requests for just-in-time access to a managed application.
4-
author: MSEvanhi
54
ms.topic: conceptual
65
ms.date: 06/24/2024
7-
ms.author: evanhi
86
---
97

108
# Configure and approve just-in-time access for Azure Managed Applications

articles/azure-resource-manager/managed-applications/concepts-built-in-policy.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
title: Deploy associations for managed application using Azure Policy
33
description: Learn about deploying associations for a managed application using Azure Policy.
4-
author: msHich
54
ms.topic: conceptual
65
ms.date: 06/24/2024
7-
ms.author: hich
86
---
97

108
# Deploy associations for a managed application using Azure Policy

articles/azure-resource-manager/managed-applications/create-storage-customer-managed-key.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Create Azure Managed Application that deploys storage account encrypted w
33
description: This article describes how to create an Azure Managed Application that deploys a storage account encrypted with a customer-managed key.
44
ms.author: jojok
55
author: jojokoshy
6+
ms.reviewer: evanhi
67
ms.topic: how-to
78
ms.date: 06/24/2024
89
---

articles/azure-resource-manager/managed-applications/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ metadata:
88
description: Azure Managed Applications enable you to offer cloud solutions that are easy for consumers to deploy and operate.
99
ms.service: azure-managed-applications
1010
ms.topic: landing-page
11-
author: davidsmatlak
12-
ms.author: davidsmatlak
11+
author: MSEvanhi
12+
ms.author: evanhi
1313
ms.date: 07/11/2024
1414

1515
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new

articles/azure-resource-manager/managed-applications/request-just-in-time-access.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
title: Request just-in-time access
33
description: Describes how publishers of Azure Managed Applications request just-in-time access to a managed application.
4-
author: MSEvanhi
54
ms.topic: conceptual
65
ms.date: 06/24/2024
7-
ms.author: evanhi
86
---
97

108
# Enable and request just-in-time access for Azure Managed Applications

articles/container-apps/.openpublishing.redirection.container-apps.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,11 @@
6464
"source_path_from_root": "/articles/container-apps/network-proxy.md",
6565
"redirect_url": "/azure/container-apps/ingress-overview",
6666
"redirect_document_id": false
67+
},
68+
{
69+
"source_path_from_root": "/articles/container-apps/hardware.md",
70+
"redirect_url": "/azure/container-apps/workload-profiles-overview",
71+
"redirect_document_id": false
6772
}
6873
]
6974
}

articles/container-apps/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -410,8 +410,6 @@
410410
href: /rest/api/containerapps/
411411
- name: Supported regions
412412
href: https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=container-apps
413-
- name: Hardware reference
414-
href: hardware.md
415413
- name: Management SDKs
416414
items:
417415
- name: .NET

articles/container-apps/containers.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: conceptual
8-
ms.date: 08/29/2023
8+
ms.date: 09/19/2024
99
ms.author: cshoe
1010
---
1111

@@ -19,11 +19,11 @@ Azure Container Apps supports:
1919

2020
- Any Linux-based x86-64 (`linux/amd64`) container image
2121
- Containers from any public or private container registry
22-
- [Sidecar](#sidecar-containers) and [init](#init-containers) containers
22+
- Optional [sidecar](#sidecar-containers) and [init](#init-containers) containers
2323

2424
Features also include:
2525

26-
- Changes to the `template` configuration section trigger a new [container app revision](application-lifecycle-management.md).
26+
- Apps use the `template` configuration section to define the container image and other settings. Changes to the `template` configuration section trigger a new [container app revision](application-lifecycle-management.md).
2727
- If a container crashes, it automatically restarts.
2828

2929
Jobs features include:
@@ -286,6 +286,10 @@ Azure Container Apps has the following limitations:
286286

287287
- **Operating system**: Linux-based (`linux/amd64`) container images are required.
288288

289+
- **Maximum image size**:
290+
- Consumption workload profile supports container images totaling up to 8GB for each app or job replica.
291+
- Dedicated workload profiles support larger container images. Because a Dedicated workload profile can run multiple apps or jobs, multiple container images share the available disk space. The actual supported image size varies based on resources consumed by other apps and jobs.
292+
289293
## Next steps
290294

291295
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)