Skip to content

Commit 60843a4

Browse files
author
Tristan Desktop
committed
v1 changes pushed with diagram placeholders
1 parent 9791f9a commit 60843a4

File tree

5 files changed

+39
-1
lines changed

5 files changed

+39
-1
lines changed
106 KB
Loading

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-aws.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,20 @@ This article describes how to onboard an Amazon Web Services (AWS) account on Pe
1818
> [!NOTE]
1919
> A *global administrator* or *super admin* (an admin for all authorization system types) can perform the tasks in this article after the global administrator has initially completed the steps provided in [Enable Permissions Management on your Azure Active Directory tenant](onboard-enable-tenant.md).
2020
21+
## Explanation
22+
23+
There are several moving parts across AWS and Azure which are required to be configured before onboarding.
24+
25+
1. An AAD OIDC App
26+
1. An AWS OIDC account
27+
1. An (optional) AWS Master account
28+
1. An (optional) AWS Central logging account
29+
1. An AWS OIDC role
30+
1. An AWS Cross Account role assumed by OIDC role
31+
32+
33+
<!-- diagram from gargi -->
34+
2135
## Onboard an AWS account
2236

2337
1. If the **Data Collectors** dashboard isn't displayed when Permissions Management launches:

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-azure.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,14 @@ This article describes how to onboard a Microsoft Azure subscription or subscrip
1818
> [!NOTE]
1919
> A *global administrator* or *super admin* (an admin for all authorization system types) can perform the tasks in this article after the global administrator has initially completed the steps provided in [Enable Permissions Management on your Azure Active Directory tenant](onboard-enable-tenant.md).
2020
21+
## Explanation
22+
23+
Given Permissions Management is hosted on Azure and you are onboarding your Azure subscriptions to be monitored and managed, setup is simple with few moving parts to configure. Below is what is required to configure onboarding:
24+
25+
1. When your tenant is onboarded, an application is created in the tenant.
26+
1. This app requires 'reader' permissions on the subscriptions
27+
1. For controller functionality, the app requires 'User Access Administrator' to create and implement right-size roles
28+
2129
## Prerequisites
2230

2331
To add Permissions Management to your Azure AD tenant:

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-enable-tenant.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ This article describes how to enable Permissions Management in your organization
1818
> [!NOTE]
1919
> To complete this task, you must have *global administrator* permissions as a user in that tenant. You can't enable Permissions Management as a user from other tenant who has signed in via B2B or via Azure Lighthouse.
2020
21+
:::image type="content" source="media/onboard-enable-tenant/dashboard.png" alt-text="A preview of what the permissions management dashboard looks like." lightbox="media/onboard-enable-tenant/dashboard.png":::
22+
2123
## Prerequisites
2224

2325
To enable Permissions Management in your organization:

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-gcp.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,20 @@ This article describes how to onboard a Google Cloud Platform (GCP) project on P
1818
> [!NOTE]
1919
> A *global administrator* or *super admin* (an admin for all authorization system types) can perform the tasks in this article after the global administrator has initially completed the steps provided in [Enable Permissions Management on your Azure Active Directory tenant](onboard-enable-tenant.md).
2020
21+
## Explanation
22+
23+
For GCP, permissions management is scoped to a *GCP project*. A GCP project is a logical collection of your resources in GCP, somewhat analogous to a subscription in Azure, albeit with further configurations you can perform e.g. application registrations.
24+
25+
<!-- Diagram from Gargi-->
26+
27+
There are several moving parts across GCP and Azure which are required to be configured before onboarding.
28+
29+
1. An AAD OIDC App
30+
1. An Workload Identity in GCP
31+
1. OAuth2 confidential client grant utilized
32+
1. A GCP service account with permissions to collect
33+
34+
2135
## Onboard a GCP project
2236

2337
1. If the **Data Collectors** dashboard isn't displayed when Permissions Management launches:
@@ -108,7 +122,7 @@ This option detects all projects that are accessible by the Cloud Infrastructure
108122
109123
The **Welcome to Permissions Management GCP onboarding** screen appears, displaying steps you must complete to onboard your GCP project.
110124

111-
### 5. Paste the environment vars from the Permissions Management portal.
125+
### 5. Paste the environmental variables from the Permissions Management portal.
112126

113127
1. Return to Permissions Management and select **Copy export variables**.
114128
1. In the GCP Onboarding shell editor, paste the variables you copied, and then press **Enter**.

0 commit comments

Comments
 (0)