Tom Bamford

@jrasanen Thanks for pointing this out! As this is a Resource Manager API, the corresponding resource to create/manage a B2C tenant and it's subscription association will be implemented in the...

@jarifibrahim We would definitely like to support this, however we are first looking to implement support in the provider for pinning, or otherwise asserting, the API version - due to...

Hi @tsologub, thanks for the detailed report. This possibly requires `User.Read.All` in order to retrieve the other user owner, whereas retrieving the object for oneself is implicitly allowed. Does this...

Thanks @tsologub, that correlates with my expectations. With a default configuration, service principals are readable by anyone. I'll factor this in and see what I can come up with. We...

@tsologub I believe #713 should resolve this. We don't actually need to call the `/directoryObjects` endpoint any more, at least for applications or service principals. Managing owners for groups will...

Hi @tsologub, the PR made sense to merge even if it did not necessarily fix the issue, although I intended to not close the issue - so I've reopened it....

@tsologub Thanks for the information on the workaround. I have noticed several times when creating applications with no specified owners, that sometimes the app will be auto-assigned the caller as...

Hi @josh-barker, thanks for reporting this. I believe the error during recreate is due to an eventual consistency issue with the API, which we might be able to mitigate. For...

May be related to #535

This would usually be taken care of by the DAG if you reference the `application_id` in the service principal resource, from the application resource - I'll play around with this...