Skip to content

Commit 8a25e25

Browse files
authored
Merge pull request #190380 from bandersmsft/ghissue88770
CMB - Updated for github issue 88770
2 parents 92f7187 + 8a5b93f commit 8a25e25

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.reviewer: sapnakeshari
66
ms.service: cost-management-billing
77
ms.subservice: enterprise
88
ms.topic: conceptual
9-
ms.date: 10/22/2021
9+
ms.date: 03/02/2022
1010
ms.author: banders
1111
ms.custom: contperf-fy21q1
1212
---
@@ -87,6 +87,8 @@ Users with this role have the highest level of access. They can:
8787

8888
You can have multiple enterprise administrators in an enterprise enrollment. You can grant read-only access to enterprise administrators. They all inherit the department administrator role.
8989

90+
The enterprise administrator role can be assigned to multiple accounts.
91+
9092
### EA purchaser
9193

9294
Users with this role have permissions to purchase Azure services, but are not allowed to manage accounts. They can:
@@ -121,6 +123,8 @@ Users with this role can:
121123

122124
Each account requires a unique work, school, or Microsoft account. For more information about Azure Enterprise portal administrative roles, see [Understand Azure Enterprise Agreement administrative roles in Azure](understand-ea-roles.md).
123125

126+
There can be only one account owner per account. However, there can be multiple accounts in an EA enrollment. Each account has a unique account owner.
127+
124128
### Service administrator
125129

126130
The service administrator role has permissions to manage services in the Azure portal and assign users to the coadministrator role.

0 commit comments

Comments
 (0)