Skip to content

Commit e4f9eb1

Browse files
authored
Merge pull request #248638 from jenniferf-skc/day0quickstart
New PM Quickstart Guide and Roles + Permissions article
2 parents f61d1ba + 50118de commit e4f9eb1

File tree

3 files changed

+255
-2
lines changed

3 files changed

+255
-2
lines changed

articles/active-directory/cloud-infrastructure-entitlement-management/TOC.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@
88
- name: How-to guides
99
expanded: true
1010
items:
11-
- name: Trial user guide - Microsoft Entra Permissions Management
12-
href: permissions-management-trial-user-guide.md
11+
- name: Quickstart guide - Microsoft Entra Permissions Management
12+
href: permissions-management-quickstart-guide.md
1313
- name: Onboard Permissions Management on the Azure AD tenant
1414
expanded: true
1515
items:
@@ -65,6 +65,8 @@
6565
- name: Manage roles/policies and permission requests
6666
expanded: false
6767
items:
68+
- name: Permissions Management roles and permissions
69+
href: product-roles-permissions.md
6870
- name: View privileged role assignments in your organization
6971
href: product-privileged-role-insights.md
7072
- name: View roles/policies and requests for permission in the Remediation dashboard
Lines changed: 184 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,184 @@
1+
---
2+
title: Microsoft Entra Permissions Management Quickstart Guide
3+
description: Quickstart guide - How to quickly onboard your Microsoft Entra Permissions Management product
4+
# CustomerIntent: As a security administrator, I want to successfully onboard Permissions Management so that I can enable identity security in my cloud environment as efficiently as possible.'
5+
services: active-directory
6+
author: jenniferf-skc
7+
manager: amycolannino
8+
ms.service: active-directory
9+
ms.subservice: ciem
10+
ms.workload: identity
11+
ms.topic: quickstart
12+
ms.date: 08/24/2023
13+
ms.author: jfields
14+
---
15+
16+
# Quickstart guide to Microsoft Entra Permissions Management
17+
18+
Welcome to the Quickstart Guide for Microsoft Entra Permissions Management.
19+
20+
Permissions Management is a Cloud Infrastructure Entitlement Management (CIEM) solution that provides comprehensive visibility into permissions assigned to all identities. These identities include over-privileged workload and user identities, actions, and resources across multicloud infrastructures in Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP). Permissions Management helps your organization effectively secure and manage cloud permissions by detecting, automatically right-sizing, and continuously monitoring unused and excessive permissions.
21+
22+
With this quickstart guide, you’ll set up your multicloud environment(s), configure data collection, and enable permissions access to ensure your cloud identities are managed and secure.
23+
24+
## Prerequisites
25+
26+
Before you begin, you need access to these tools for the onboarding process:
27+
28+
- Access to a local BASH shell with the Azure CLI or Azure Cloud Shell using BASH environment (Azure CLI is included).
29+
- Access to AWS, Azure, and GCP consoles.
30+
- A user must have *Global Administrator* or *Permissions Management Administrator* role assignments to create a new app registration in Entra ID tenant is required for AWS and GCP onboarding.
31+
32+
33+
## Step 1: Set-up Permissions Management
34+
35+
To enable Permissions Management, you must have a Microsoft Entra ID tenant (example, Entra admin center).
36+
- If you have an Azure account, you automatically have an Entra admin center tenant.
37+
- If you don’t already have one, create a free account at [entra.microsoft.com.](https://entra.microsoft.com)
38+
39+
If the above points are met, continue with:
40+
41+
[Enable Microsoft Entra Permissions Management in your organization](onboard-enable-tenant.md)
42+
43+
Ensure you're a *Global Administrator* or *Permissions Management Administrator*. Learn more about [Permissions Management roles and permissions](product-roles-permissions.md).
44+
45+
46+
## Step 2: Onboard your multicloud environment
47+
48+
So far you’ve,
49+
50+
1. Been assigned the *Permissions Management Administrator* role in your Entra admin center tenant.
51+
2. Purchased licenses or activated your 45-day free trial for Permissions Management.
52+
3. Successfully launched Permissions Management.
53+
54+
Now, you're going to learn about the role and settings of the Controller and Data collection modes in Permissions Management.
55+
56+
### Set the controller
57+
The controller gives you the choice to determine the level of access you grant to users in Permissions Management.
58+
59+
- Enabling the controller during onboarding grants Permissions Management admin access, or read and write access, so users can right-size permissions and remediate directly through Permissions Management (instead of going to the AWS, Azure, or GCP consoles). 
60+
61+
- Disabling the controller during onboarding, or never enabling it, grants a Permissions Management user read-only access to your environment(s).
62+
63+
> [!NOTE]
64+
> If you don't enable the controller during onboarding, you have the option to enable it after onboarding is complete. To set the controller in Permissions Management after onboarding, see [Enable or disable the controller after onboarding](onboard-enable-controller-after-onboarding.md).
65+
> For AWS environments, once you have enabled the controller, you *cannot* disable it.
66+
67+
To set the controller settings during onboarding:
68+
1. Select **Enable** to give read and write access to Permissions Management.
69+
2. Select **Disable** to give read-only access to Permissions Management.
70+
71+
### Configure data collection
72+
73+
There are three modes to choose from in order to collect data in Permissions Management.
74+
75+
- **Automatic (recommended)**
76+
Permissions Management automatically discovers, onboards, and monitors all current and future subscriptions.
77+
78+
- **Manual**
79+
Manually enter individual subscriptions for Permissions Management to discover, onboard, and monitor. You can enter up to 100 subscriptions per data collection.
80+
81+
- **Select**
82+
Permissions Management automatically discovers all current subscriptions. Once discovered, you select which subscriptions to onboard and monitor.
83+
84+
> [!NOTE]
85+
> To use **Automatic** or **Select** modes, the controller must be enabled while configuring data collection.
86+
87+
To configure data collection:
88+
1. In Permissions Management, navigate to the data collectors page.
89+
2. Select a cloud environment: AWS, Azure, or GCP.
90+
3. Click **Create configuration**.
91+
92+
### Onboard Amazon Web Services (AWS)
93+
Since Permissions Management is hosted on Microsoft Entra, there are more steps to take to onboard your AWS environment.
94+
95+
To connect AWS to Permissions Management, you must create an Entra ID application in the Entra admin center tenant where Permissions Management is enabled. This Entra ID application is used to set up an OIDC connection to your AWS environment.
96+
97+
*OpenID Connect (OIDC) is an interoperable authentication protocol based on the OAuth 2.0 family of specifications.*
98+
99+
### Prerequisites
100+
101+
A user must have *Global Administrator* or *Permissions Management Administrator* role assignments to create a new app registration in Entra ID.
102+
103+
Account IDs and roles for:
104+
- AWS OIDC account: An AWS member account designated by you to create and host the OIDC connection through an OIDC IdP
105+
- AWS Logging account (optional but recommended)
106+
- AWS Management account (optional but recommended)
107+
- AWS member accounts monitored and managed by Permissions Management (for manual mode)
108+
109+
To use **Automatic** or **Select** data collection modes, you must connect your AWS Management account.
110+
111+
During this step, you can enable the controller by entering the name of the S3 bucket with AWS CloudTrail activity logs (found on AWS Trails).
112+
113+
To onboard your AWS environment and configure data collection, see [Onboard an Amazon Web Services (AWS) account](onboard-aws.md).
114+
115+
### Onboard Microsoft Azure
116+
When you enabled Permissions Management in the Entra ID tenant, an enterprise application for CIEM was created. To onboard your Azure environment, you grant permissions to this application for Permissions management.
117+
118+
1. In the Entra ID tenant where Permissions management is enabled, locate the **Cloud Infrastructure Entitlement Management (CIEM)** enterprise application.
119+
120+
2. Assign the *Reader* role to the CIEM application to allow Permissions management to read the Entra subscriptions in your environment.
121+
122+
### Prerequisites
123+
- A user with ```Microsoft.Authorization/roleAssignments/write``` permissions at the subscription or management group scope.
124+
125+
- To use **Automatic** or **Select** data collection modes, you must assign the *Reader* role at the Management group scope.
126+
127+
- To enable the controller, you must assign the *User Access Administrator* role to the CIEM application.
128+
129+
To onboard your Azure environment and configure data collection, see [Onboard a Microsoft Azure subscription](onboard-azure.md).
130+
131+
132+
### Onboard Google Cloud Platform (GCP)
133+
Because Permissions Management is hosted on Microsoft Azure, there are additional steps to take to onboard your GCP environment.
134+
135+
To connect GCP to Permissions Management, you must create an Entra admin center application in the Entra ID tenant where Permissions Management is enabled. This Entra admin center application is used to set up an OIDC connection to your GCP environment.
136+
137+
*OpenID Connect (OIDC) is an interoperable authentication protocol based on the OAuth 2.0 family of specifications.*
138+
139+
140+
### Prerequisites
141+
A user with the ability to create a new app registration in Entra (needed to facilitate the OIDC connection) is needed for AWS and GCP onboarding.
142+
143+
ID details for:
144+
- GCP OIDC project: a GCP project designated by you to create and host the OIDC connection through an OIDC IdP.
145+
- Project number and project ID
146+
- GCP OIDC Workload identity
147+
- Pool ID, pool provider ID
148+
- GCP OIDC service account
149+
- G-suite IdP Secret name and G-suite IdP user email (optional)
150+
- IDs for the GCP projects you wish to onboard (optional, for manual mode)
151+
152+
Assign the *Viewer* and *Security Reviewer* roles to the GCP service account at the organization, folder, or project levels to grant Permissions management read access to your GCP environment.
153+
154+
During this step, you have the option to **Enable** controller mode by assigning the *Role Administrator* and *Security Administrator* roles to the GCP service account at the organization, folder, or project levels.
155+
156+
> [!NOTE]
157+
> The Permissions Management default scope is at the project level.
158+
159+
To onboard your GCP environment and configure data collection, see [Onboard a GCP project](onboard-gcp.md).
160+
161+
## Summary
162+
163+
Congratulations! You have finished configuring data collection for your environment(s), and the data collection process has begun.
164+
165+
The status column in your Permissions Management UI shows you which step of data collection you're at.
166+
167+
168+
- **Pending**: Permissions Management has not started detecting or onboarding yet.
169+
- **Discovering**: Permissions Management is detecting the authorization systems.
170+
- **In progress**: Permissions Management has finished detecting the authorization systems and is onboarding.
171+
- **Onboarded**: Data collection is complete, and all detected authorization systems are onboarded to Permissions Management.
172+
173+
> [!NOTE]
174+
> Data collection might take time depending on the amount of authorization systems you've onboarded. While the data collection process continues, you can begin setting up [users and groups in Permissions Management](how-to-add-remove-user-to-group.md).
175+
176+
## Next steps
177+
178+
- [Enable or disable the controller after onboarding](onboard-enable-controller-after-onboarding.md)
179+
- [Add an account/subscription/project after onboarding is complete](onboard-add-account-after-onboarding.md)
180+
- [Create folders to organize your authorization systems](how-to-create-folders.md)
181+
182+
References:
183+
- [Permissions Management Glossary](multi-cloud-glossary.md)
184+
- [Permissions Management FAQs](faqs.md)
Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: Microsoft Entra Permissions Management roles and permissions
3+
description: Review roles and the level of permissions assigned in Microsoft Entra Permissions Management.
4+
# customerintent: As a cloud administer, I want to understand Permissions Management role assignments, so that I can effectively assign the correct permissions to users.
5+
services: active-directory
6+
author: jenniferf-skc
7+
manager: amycolannino
8+
ms.service: active-directory
9+
ms.subservice: ciem
10+
ms.workload: identity
11+
ms.topic: how-to
12+
ms.date: 08/24/2023
13+
ms.author: jfields
14+
---
15+
16+
17+
# Microsoft Entra Permissions Management roles and permissions levels
18+
19+
In Microsoft Azure and Microsoft Entra Permissions Management role assignments grant users permissions to monitor and take action in multicloud environments.
20+
21+
- **Global Administrator**: Manages all aspects of Entra Admin Center and Microsoft services that use Entra Admin Center identities.
22+
- **Billing Administrator**: Performs common billing related tasks like updating payment information.
23+
- **Permissions Management Administrator**: Manages all aspects of Entra Permissions Management.
24+
25+
See [Microsoft Entra ID built-in roles to learn more.](product-privileged-role-insights.md)
26+
27+
## Enabling Permissions Management
28+
- To activate a trial or purchase a license, you must have *Global Administrator* or *Billing Administrator* permissions.
29+
30+
## Onboarding your Amazon Web Service (AWS), Microsoft Entra, or Google Cloud Platform (GCP) environments
31+
32+
- To configure data collection, you must have *Permissions Management Administrator* or *Global Administrator* permissions.
33+
- A user with *Global Administrator* or *Permissions Management Administrator* role assignments is required for AWS and GCP onboarding.
34+
35+
## Notes on permissions and roles in Permissions Management
36+
37+
- Users can have the following permissions:
38+
- Admin for all authorization system types
39+
- Admin for selected authorization system types
40+
- Fine-grained permissions for all or selected authorization system types
41+
- If a user isn't an admin, they're assigned Microsoft Entra ID security group-based, fine-grained permissions for all or selected authorization system types:
42+
- Viewers: View the specified AWS accounts, Azure subscriptions, and GCP projects
43+
- Controller: Modify Cloud Infrastructure Entitlement Management (CIEM) properties and use the Remediation dashboard.
44+
- Approvers: Able to approve permission requests
45+
- Requestors: Request permissions in the specified AWS accounts, Entra subscriptions, and GCP projects.
46+
47+
## Permissions Management actions and required roles
48+
49+
Remediation
50+
- To view the **Remediation** tab, you must have *Viewer*, *Controller*, or *Approver* permissions.
51+
- To make changes in the **Remediation** tab, you must have *Controller* or *Approver* permissions.
52+
53+
Autopilot
54+
- To view and make changes in the **Autopilot** tab, you must be a *Permissions Management Administrator*.
55+
56+
Alert
57+
- Any user (admin, nonadmin) can create an alert.
58+
- Only the user who creates the alert can edit, rename, deactivate, or delete the alert.
59+
60+
Manage users or groups
61+
- Only the owner of a group can add or remove a user from the group.
62+
- Managing users and groups is only done in the Entra Admin Center.
63+
64+
65+
## Next steps
66+
67+
For information about managing roles, policies and permissions requests in your organization, see [View roles/policies and requests for permission in the Remediation dashboard](ui-remediation.md).

0 commit comments

Comments
 (0)