Skip to content

Commit f04d1e2

Browse files
authored
Merge pull request #292139 from MicrosoftDocs/main
12/18/2024 AM Publish
2 parents 260daeb + f97cb4b commit f04d1e2

35 files changed

+306
-187
lines changed

articles/app-service/overview-tls.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ For App Service Environments with `FrontEndSSLCipherSuiteOrder` cluster setting,
7979

8080
## End-to-end TLS Encryption
8181

82-
End-to-end (E2E) TLS encryption is available in Standard App Service plans and higher. Front-end intra-cluster traffic between App Service front-ends and the workers running application workloads can now be encrypted.
82+
End-to-end (E2E) TLS encryption is available in Premium App Service plans (and legacy Standard App Service plans). Front-end intra-cluster traffic between App Service front-ends and the workers running application workloads can now be encrypted.
8383

8484
## Next steps
8585
* [Secure a custom DNS name with a TLS/SSL binding](configure-ssl-bindings.md)

articles/application-gateway/configuration-infrastructure.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,24 @@ Check your [Azure role-based access control](../role-based-access-control/role-a
7878

7979
You can use the built-in roles, such as [Network contributor](../role-based-access-control/built-in-roles.md#network-contributor), which already support these permissions. If a built-in role doesn't provide the right permission, you can [create and assign a custom role](../role-based-access-control/custom-roles-portal.md). Learn more about [managing subnet permissions](../virtual-network/virtual-network-manage-subnet.md#permissions).
8080

81+
## Permissions
82+
Depending on whether you're creating new resources or using existing ones, add the appropriate permissions from the following list:
83+
84+
|Resource | Resource status | Required Azure permissions |
85+
|---|---|---|
86+
| Subnet | Create new| Microsoft.Network/virtualNetworks/subnets/write<br>Microsoft.Network/virtualNetworks/subnets/join/action |
87+
| Subnet | Use existing| Microsoft.Network/virtualNetworks/subnets/read<br>Microsoft.Network/virtualNetworks/subnets/join/action |
88+
| IP addresses| Create new| Microsoft.Network/publicIPAddresses/write<br>Microsoft.Network/publicIPAddresses/join/action |
89+
| IP addresses | Use existing| Microsoft.Network/publicIPAddresses/read<br>Microsoft.Network/publicIPAddresses/join/action |
90+
| ApplicationGatewayWebApplicationFirewallPolicies | Create new / Update existing | Microsoft.Network/ApplicationGatewayWebApplicationFirewallPolicies/write Microsoft.Network/ApplicationGatewayWebApplicationFirewallPolicies/join/action |
91+
92+
For more information, see [Azure permissions for Networking](../role-based-access-control/permissions/networking.md) and [Virtual network permissions](../virtual-network/virtual-network-manage-subnet.md#permissions).
93+
## Roles scope
94+
In the process of custom role definition, you can specify a role assignment scope at four levels: management group, subscription, resource group, and resources. To grant access, you assign roles to users, groups, service principals, or managed identities at a particular scope.
95+
These scopes are structured in a parent-child relationship, with each level of hierarchy making the scope more specific. You can assign roles at any of these levels of scope, and the level you select determines how widely the role is applied.
96+
For example, a role assigned at the subscription level can cascade down to all resources within that subscription, while a role assigned at the resource group level will only apply to resources within that specific group. Learn more about scope level
97+
For more information, see [Scope levels](../role-based-access-control/scope-overview.md#scope-levels).
98+
8199
> [!NOTE]
82100
> You might have to allow sufficient time for [Azure Resource Manager cache refresh](../role-based-access-control/troubleshooting.md?tabs=bicep#symptom---role-assignment-changes-are-not-being-detected) after role assignment changes.
83101
@@ -221,3 +239,5 @@ Any scenario where 0.0.0.0/0 needs to be redirected through a virtual appliance,
221239

222240
- [Learn about frontend IP address configuration](configuration-frontend-ip.md)
223241
- [Learn about private Application Gateway deployment](application-gateway-private-deployment.md)
242+
- [What is Azure Role Based Access](../role-based-access-control/overview.md)
243+
- [Azure Role Based Access Control](../role-based-access-control/role-assignments-list-portal.yml)

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ Configuring UDRs on the source VM subnets with the address prefix of delegated s
111111
> To access an Azure NetApp Files volume from an on-premises network via a VNet gateway (ExpressRoute or VPN) and firewall, configure the route table assigned to the VNet gateway to include the `/32` IPv4 address of the Azure NetApp Files volume listed and point to the firewall as the next hop. Using an aggregate address space that includes the Azure NetApp Files volume IP address will not forward the Azure NetApp Files traffic to the firewall.
112112
113113
>[!NOTE]
114-
> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual alliance or firewall destined to an Azure NetApp Files standard volume from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Azure NetApp Files volume. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective.
114+
> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual appliance or firewall destined to an Azure NetApp Files standard volume from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Azure NetApp Files volume. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective.
115115
>
116116
> For example, if your delegated subnet is `x.x.x.x/24`, you must configured your UDR to `x.x.x.x/24` (equal) or `x.x.x.x/32` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall.
117117

articles/backup/backup-azure-diagnostic-events.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,9 @@ Azure Backup sends diagnostics events that can be collected and used for the pur
1717

1818
You can configure diagnostics settings for a Recovery Services vault via the Azure portal by going to the vault and selecting **Diagnostics settings**. Selecting **+ Add Diagnostic Setting** lets you send one or more diagnostic events to a storage account, an event hub, or a Log Analytics workspace.
1919

20+
> [!NOTE]
21+
> Recovery Services vaults can send diagnostic logs to a storage account located in the same region. They can also send these logs to a Log Analytics workspace that may be situated in either the same or a different region.
22+
2023
![Diagnostics settings pane](./media/backup-azure-diagnostics-events/diagnostics-settings-blade.png)
2124

2225
## Diagnostics events available for Azure Backup users

articles/backup/blob-backup-support-matrix.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Support matrix for Azure Blobs backup
33
description: Provides a summary of support settings and limitations when backing up Azure Blobs.
44
ms.topic: reference
5-
ms.date: 12/03/2024
5+
ms.date: 12/18/2024
66
ms.custom: references_regions, engagement-fy24
77
ms.service: azure-backup
88
author: AbhishekMallick-MS
@@ -67,9 +67,10 @@ Operational backup of blobs uses blob point-in-time restore, blob versioning, so
6767
- When you delete and recreate a storage account with the same name, **Object Replication** doesn't recognize the change. As a result, future Recovery Points continue to include the older blobs and their versions.
6868
- Similarly, if you delete and recreate a container with the same name, **Object Replication** doesn't track the change, and future Recovery Points still include the previous blobs and versions.
6969
- If you suspend and resume protection or delete the **Object Replication policy** on the **source storage account**, the policy triggers a full backup.
70-
70+
- Backup vaults with User-Assigned Managed Identity (UAMI) aren't compatible with Azure Blob Vaulted backups. Only System-Assigned Managed Identity (SAMI) works, because the vault needs to access the storage account where the blobs are stored. The vault uses its system-assigned managed identity for this access.
7171

7272
---
73+
7374
## Next steps
7475

7576
[Overview of Azure Blobs backup for Azure Blobs](blob-backup-overview.md)

articles/backup/manage-afs-backup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Manage Azure File share backups
33
description: This article describes common tasks for managing and monitoring the Azure File shares that are backed up by Azure Backup.
44
ms.topic: how-to
5-
ms.date: 09/11/2024
5+
ms.date: 12/18/2024
66
ms.service: azure-backup
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
@@ -198,7 +198,7 @@ To delete backup data for the Azure File share:
198198

199199
## Unregister a storage account
200200

201-
To protect your file shares in a particular storage account by using a different Recovery Services vault, first [stop protection for all file shares](#stop-protection-on-a-file-share) in that storage account. Then unregister the account from the current Recovery Services vault used for protection.
201+
To protect your file shares in a particular storage account by using a different Recovery Services vault, first [stop protection for all file shares](#stop-protection-on-a-file-share) with the **Delete backup data** option in that storage account. Then unregister the account from the current Recovery Services vault used for protection.
202202

203203
The following procedure assumes that the protection was stopped for all file shares in the storage account you want to unregister.
204204

articles/cdn/edgio-retirement-faq.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,6 @@ Consider whether Akamai or another CDN provider might be compatible with your ne
4242

4343
If you find that Azure Front Door isn't suitable for your workload, we offer an alternative service called [Routing Preference Unmetered](../virtual-network/ip-services/routing-preference-unmetered.md), also known as "CDN Interconnect." This service might allow free data transfer for traffic egressing from your Azure resources to another CDN of your choice.
4444

45-
Additionally, you can choose to continue working directly with Edgio to minimize interruptions, keeping your origins on Azure while utilizing Edgio's services. For further information, contact Microsoft Support or reach out to [Edgio](https://edg.io/contact-us/).
46-
4745
### Does Microsoft validate my workloads work on Azure Front Door?
4846

4947
You need to determine if Azure Front Door suits your workloads. We recommend setting up a test environment to validate that your services are compatible with Azure Front Door.

articles/cost-management-billing/manage/cloud-subscription.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ A cloud subscription is a way to manage the products and services that you buy f
1717

1818
The term cloud subscription is synonymous with Azure subscription.
1919

20-
- **No cost for cloud subscriptions** - Cloud subscriptions themselves don't cost any money. They're used to organizing and managing the things you buy. While products like virtual machines or Enterprise Support managed within a cloud subscription might incur charges, the subscription itself doesn't.
20+
- **No cost for cloud subscriptions** - Cloud subscriptions themselves don't cost any money. They're used to organize and manage the things you buy. While products like virtual machines or Enterprise Support managed within a cloud subscription might incur charges, the subscription itself doesn't.
2121
- **Multiple subscriptions** - You can create multiple cloud subscriptions to delegate management to different users in your organization or to apply policies for security, budgeting, and compliance.
2222
- **Familiar management tools** - If you used Azure subscriptions before, you can manage cloud subscriptions similarly, with more manageability for a broader set of products and services.
2323

@@ -36,7 +36,7 @@ If you're signing in for the first time, search for **Subscriptions** in the sea
3636

3737
### Do I get charged for creating and using cloud subscriptions?
3838

39-
No, cloud subscriptions are created silently and are used to manage the things that you buy. They don't incur charges or cost money.
39+
No. Cloud subscriptions get created on the back end and are used to manage the things that you buy. They don't incur charges or cost money.
4040

4141
### How do I manage my cloud subscriptions?
4242

articles/cost-management-billing/manage/download-azure-invoice-daily-usage-date.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ You can opt out of getting your invoice by email by following the preceding step
8787

8888
### Get your Microsoft Customer Agreement invoices in email
8989

90-
If you have a Microsoft Customer Agreement, you can opt in to get your invoice in an email. All billing profile Owners, Contributors, Readers, and Invoice managers will get the invoice by email. Readers can't update the email invoice preference.
90+
If you have a Microsoft Customer Agreement, you can opt in to get your invoice in an email. All billing profile Owners, Contributors, Readers, and Invoice managers will get the invoice by email. Readers can't update the email invoice preference. Please note that if you have inherited a role from the Billing Account, you will not receive invoices. Access must be granted explicitly under the Billing profile.
9191

9292
1. Search for **Cost Management + Billing**.
9393
1. Select a billing profile.

articles/cost-management-billing/manage/understand-ea-roles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ Use Cost Management in the [Azure portal](https://portal.azure.com) so you can m
6969

7070
Direct EA customers can complete all administrative tasks in the Azure portal. You can use the [Azure portal](https://portal.azure.com) to manage billing, costs, and Azure services.
7171

72-
User roles are associated with a user account. To validate user authenticity, each user must have a valid work, school, or Microsoft account. Ensure that each account is associated with an email address to actively monitor it. Enrollment notifications are sent to the email address.
72+
EA Billing roles can only be assigned to individual user accounts. Assigning these roles to Distribution Groups (DGs) and Security Groups (SGs) is not supported. To validate user authenticity, each user must have a valid work, school, or Microsoft account. Ensure that each account is associated with an email address to actively monitor it. Enrollment notifications are sent to the email address.
7373

7474
> [!NOTE]
7575
> The Account Owner role is often assigned to a service account that doesn't have an actively monitored email.

0 commit comments

Comments
 (0)