Skip to content

Commit aefc138

Browse files
committed
Merge branch 'patch-2' of https://github.com/shyambasnet1/azure-docs into rs-faq
2 parents 0b4c437 + d3e18ff commit aefc138

File tree

3 files changed

+9
-2
lines changed

3 files changed

+9
-2
lines changed

articles/role-based-access-control/role-definitions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ Role-based access control for control plane actions is specified in the `Actions
179179
- Create, update, or delete a blob container
180180
- Delete a resource group and all of its resources
181181

182-
Control plane access is not inherited to your data plane provided that the container authentication method is set to **Azure AD User Account** and not **Access Key**. This separation prevents roles with wildcards (`*`) from having unrestricted access to your data. For example, if a user has a [Reader](built-in-roles.md#reader) role on a subscription, then they can view the storage account, but by default they can't view the underlying data.
182+
Control plane access is not inherited to your data plane provided that the container authentication method is set to **Microsoft Entra User Account** and not **Access Key**. This separation prevents roles with wildcards (`*`) from having unrestricted access to your data. For example, if a user has a [Reader](built-in-roles.md#reader) role on a subscription, then they can view the storage account, but by default they can't view the underlying data.
183183

184184
Previously, role-based access control was not used for data actions. Authorization for data actions varied across resource providers. The same role-based access control authorization model used for control plane actions has been extended to data plane actions.
185185

articles/role-based-access-control/troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -250,7 +250,7 @@ At line:1 char:1
250250
If you get this error message, make sure you also specify the `-Scope` or `-ResourceGroupName` parameters.
251251

252252
```
253-
PS C:\> Remove-AzRoleAssignment -ObjectId 33333333-3333-3333-3333-333333333333 -RoleDefinitionName "Storage Blob Data Contributor" - Scope /subscriptions/11111111-1111-1111-1111-111111111111
253+
PS C:\> Remove-AzRoleAssignment -ObjectId 33333333-3333-3333-3333-333333333333 -RoleDefinitionName "Storage Blob Data Contributor" -Scope /subscriptions/11111111-1111-1111-1111-111111111111
254254
```
255255

256256
### Symptom - Cannot delete the last Owner role assignment

articles/route-server/route-server-faq.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,13 @@ No, Azure Route Server provides transit only between ExpressRoute and Site-to-Si
135135

136136
No. The spoke VNet can't have a Route Server if it's connected to the virtual WAN hub.
137137

138+
139+
### If Network Virtual Appliance has AS path prepend configured towards the route server, will the ExpressRoute circuit pass the AS path prepend information to the on-premises router?
140+
141+
No. When ExpressRoute advertises routes to on-premises, it removes the private BGP ASN, and you will only see the ExpressRoute circuit ASN
142+
143+
144+
138145
## Limitations
139146

140147
### How many Azure Route Servers can I create in a virtual network?

0 commit comments

Comments
 (0)