-
Notifications
You must be signed in to change notification settings - Fork 229
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
[CoE Starter Kit - Feature]: Update Kit to respond to new Power Platform Admin Role PIM feature #8016
Comments
Have a workaround documented : #8119 |
Build with this fix is available in the Preview Build Release, with a ship target of August 2024. Note this build is the July release plus just these two fixes for these two issues |
An early release of the August bits are available for testing. Please test for us! But do not install these in your production environment but rather in a test envt to get us feedback. Here are the August release candidate solutions. And the PBIT files It contains all the changes targeting August: https://github.com/orgs/microsoft/projects/195/views/59 Including these two very impactful changes: |
fixed in August release https://github.com/microsoft/coe-starter-kit/releases/tag/CoEStarterKit-August2024 |
Regarding the upcoming change to the Power Platform Admin Role to be dynamic - (aka PPAdmin PIM feature)
The basics of that change is that people in these admin roles will no longer be added to all envts as Sys Admin SR.
This will break our kit as it exists in that new envts will get inventoried, as the role still works to get information via things like the Power Platform admin pages and connectors, however when you try to access the data in those envts via the Dataverse connector, it will not have access.
The feature:
Manage admin roles with Microsoft Entra Privileged Identity Management:
The limitation:
Known Limitations
![image](https://private-user-images.githubusercontent.com/89584709/311718038-552e5e9c-79c5-4791-b732-1820710dbffe.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNTY4NzAsIm5iZiI6MTczOTE1NjU3MCwicGF0aCI6Ii84OTU4NDcwOS8zMTE3MTgwMzgtNTUyZTVlOWMtNzljNS00NzkxLWI3MzItMTgyMDcxMGRiZmZlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDAzMDI1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ3NDRmNDQwY2E0OWU5ODMyOThjODk4NTFhYmIyZjFmODkyMGUxMjRiZjRiNzk4ZGFmNDM1NDZjZWY1YzNkNDQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.b1QzVNJq4N91odYqaNNEJjy6zTk6UTFWqYKiWFrJNJ4)
The existing workaround
There are existing steps to elevate the user and hence be added.
However these are not in a form that the kit can consume yet. The product team is actively working to unblock us but we are not yet able to do this elevation for you.
Describe the solution you'd like
Product team adding to the Power Platform V2 connector at which point we will consume.
The text was updated successfully, but these errors were encountered: