-
Notifications
You must be signed in to change notification settings - Fork 532
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
[IntuneDeviceEnrollmentPlatformRestriction] Tenant is not Global Admin or Intune Service Admin. Operation is restricted. #5127
Comments
I never reported it but I'm also having this issue |
I opened a Microsoft case from my test tenant. Update-MgBetaDeviceManagementDeviceEnrollmentConfiguration does not work (#2410031420002336). |
Well, my ticket was closed because it would be "root cause analysis" and not "break fix". Guess I'll have to open one with the unified support then... Will keep you updated. |
Got confirmation from the unified support that there is a restriction in place that only allows updating the configuration from within the Intune portal and not via PowerShell. The product group is aware of it and will be addressing it, but no ETA was given to me. |
@srozemuller Unfortunately nothing new. We'll have to wait. |
Hi @FabienTschanz, Thank you! |
@CovidtheDog2024 I don't know, but my guess would be something in the region of spring 2024. Back in about December 2023, I implemented a full refactor of the resource and during that time, it worked without issues. Sometime later, it started to fail. |
I spoke with the MSFT productteam and can say this is by design. See : https://learn.microsoft.com/en-us/mem/intune/fundamentals/whats-new#device-enrollment-9 |
@srozemuller Thanks for the link, explains when and how the functionality is supposed to be, but doesn't help since this broke every access via Graph API. Are you telling that there is no way this will ever work again? If yes, then we most likely have to remove the resource because it's not possible to apply the state correctly which would be very sad 😢 |
Trying not to tell to much because of NDA but in fact the ability to write and update will not come back. It has something to do with RBAC philosophy and the impact of the setting. GET request still work and could be used to generate backups for example. I suggested some ideas to the team how to make it work in some way. I'm not using DSC but developing automation solutions where this is topic is needed as well. |
I tested using a user account with the Intune Administrator role, and it was successful without any errors. However, when using a Service Principal, I encountered an error. I have assigned the Service Principal the roles of Intune Administrator and Global Administrator, and ensured that the necessary API permissions are in place, but it is still failing. |
@CovidtheDog2024 This is because there is a check in place that prohibits changes to the enrollment restrictions if the calling party is not coming from the Intune portal. I got that verified with the unified support. That's why service principals are failing but interactive users are working (because users come from the Intune portal, and the service principal is via Graph API directly). |
@NikCharlebois @ykuijs @ricmestre How would you like to proceed with this issue? As @srozemuller stated, the product group won't be changing it (for the foreseeable future at least), so changes to the enrollment restrictions cannot be remediated to the state they should be in. Do we still want to include it for the export and get, but output a warning and do nothing in the set method? And what should test return if there is a diff? |
That is by design and exactly how it should work. |
Description of the issue
When trying to deploy a IntuneDeviceEnrollmentPlatformRestriction I am getting an error:
The used enterprise application has the required permissions:
The app is also assigned global admin in the tenant.
Export of the resource using the same app works fine, deploying other resource types also works fine.
Microsoft 365 DSC Version
1.24.904.1
Which workloads are affected
Intune
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: