-
Notifications
You must be signed in to change notification settings - Fork 776
Update pim-how-to-activate-role.yml #1709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Learn Build status updates of commit 5b6a0b0: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
docs/id-governance/privileged-identity-management/pim-how-to-activate-role.yml
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. |
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
@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] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
>[!IMPORTANT] | |
>[!IMPORTANT] |
There was a problem hiding this comment.
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.
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