Skip to content

Commit 0e80c7a

Browse files
authored
Apply suggestions from code review
1 parent d9a043b commit 0e80c7a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/purview/register-scan-power-bi-tenant-cross-tenant.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Use either of the following deployment checklists during the setup, or for troub
7070
1. Client ID matches the _Application (Client) ID_ of the app registration.
7171
2. For **delegated auth**, username includes the user principal name, such as `[email protected]`.
7272

73-
1. In the Power BI Azure AD tenant validate the following Power BI admin user settings:
73+
1. In the Power BI Azure AD tenant, validate the following Power BI admin user settings:
7474
1. The user is assigned to the Power BI administrator role.
7575
2. At least one [Power BI license](/power-bi/admin/service-admin-licensing-organization#subscription-license-types) is assigned to the user.
7676
3. If the user is recently created, sign in with the user at least once, to make sure that the password is reset successfully, and the user can successfully initiate the session.
@@ -178,7 +178,7 @@ In Azure Active Directory Tenant, where Power BI tenant is located:
178178

179179
:::image type="content" source="./media/setup-power-bi-scan-PowerShell/security-group.png" alt-text="Screenshot of security group type.":::
180180

181-
4. Add your **service princial** to this security group. Select **Members**, then select **+ Add members**.
181+
4. Add your **service principal** to this security group. Select **Members**, then select **+ Add members**.
182182

183183
5. Search for your Microsoft Purview managed identity or service principal and select it.
184184

0 commit comments

Comments
 (0)