Skip to content

Conversation

danwdavey
Copy link

I have just encountered a customer who has this control enabled and the guidance does not match their experience. Therefore added a note that if customer are using the other control in Entra, then they won't be able to activate their PIM Roles as they have no assigned 'standing' roles

Copy link
Contributor

Learn Build status updates of commit 5b6a0b0:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
docs/id-governance/privileged-identity-management/pim-how-to-activate-role.yml ❌Error Details

docs/id-governance/privileged-identity-management/pim-how-to-activate-role.yml

  • Line 34, Column 2: [Error: yaml-syntax-error - See documentation] While scanning a block scalar, did not find expected comment or line break.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@v-dirichards
Copy link
Contributor

@barclayn

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@danwdavey
Copy link
Author

@barclayn @v-dirichards - any updates please?

@@ -30,7 +30,8 @@ introduction: |

>[!IMPORTANT]
>If a user activating an administrative role is signed in to Microsoft Teams on a mobile device, they will receive a notification from the Teams app saying "Open Teams to continue receiving notifications for *<email address>*", or "*<email address>* needs to sign in to see notifications". The user will need to open the Teams app to continue receiving notifications. This behavior is by design.

>[!IMPORTANT]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
>[!IMPORTANT]
>[!IMPORTANT]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change should clear the build error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants