Open XVincentX opened 1 month ago
May I suggest to the Graph folks to may be align with Bicep team due to this issue seems very similar to https://github.com/Azure/bicep/issues/1895. In short Azure has the same problems with built-in roles, policy definitions, etc. May be the solution they are planning could help in Graph resource provider.
To be honest @slavizh, I would want this improved/fixed in the Microsoft Graph APIs. That way the improvement would be available to all callers across REST, SDKs, PS, CLI and Bicep. Otherwise just fixing in Bicep is putting lipstick on a pig, IMHO.
@dkershaw10 sure that makes sense as well.
I have been having struggles with the hardcoded IDs that are everywhere. To give an example, I was trying to create a new App Registration and put inside some scopes that I need approved for Microsoft Graph.
The problem is that the scopes, MS Graph Application ID as well as other well known Microsoft App IDs are unknown and it is relatively unclear where this information is supposed to be found.
I was able to find what I needed by looking at my current app registration manifest that I created through the UI, but otherwise I would have been lost
I think it would be useful to either have in the comments/documentation in the types with a quick link to where to find these IDs or even better a custom functions such as
getScopeID('Presence.Read.All', 'delegated')
and that would to the job for me. Same with appsgetMsftApp('Graph')
would return the ID