Skip to content
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

Required permissions and devops authentication #45

Open
Flory321 opened this issue Jan 5, 2024 · 2 comments
Open

Required permissions and devops authentication #45

Flory321 opened this issue Jan 5, 2024 · 2 comments

Comments

@Flory321
Copy link

Flory321 commented Jan 5, 2024

Hey guys,
we tried the intune package factory in our test tenant and in fact it's really an awesome tool ! It's definitely helpful for apps where versions changes a lot and which are not available in intune's ms store integration (new).

But there are following 2 things which currently blocks us from using it in production:

  1. We do not understand why the service principal needs the right "DeviceManagementRBAC.ReadWrite.All". This permission should as per my opinion only granted if it's really required.
  2. The azure devops uses a client secret as "Service Principal". Here we would need it to support "workload identity federation".

Don't get me wrong - we do honor what's there right now, but our internal guidelines block us from using it as it is now.
Are there any changes planned to address above topics?

Thanks
Florian

@aaronparker
Copy link
Owner

Authentication to Entra ID is managed with the IntuneWin32App module (I have not plans to write my own authentication methods). See: https://github.com/MSEndpointMgr/IntuneWin32App

@Flory321
Copy link
Author

thanks so much for response. Do you know why the permission "DeviceManagementRBAC.ReadWrite.All" is required?

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

No branches or pull requests

2 participants