AzureAD application creation odata.id change on microsoft side

[mreadings]

Howdy

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Seems like microsoft has changed the way they respond with @odata.id when creating an application which is causing a downstream issue on the terraform azure AD plugin which in turn causes a problem in Pulumi

https://issueexplorer.com/issue/hashicorp/terraform-provider-azuread/588

	* Could not create application: json.Marshal(): json: error calling MarshalJSON for type msgraph.Application: json: error calling MarshalJSON for type *msgraph.Owners: marshaling Owners: encountered DirectoryObject with nil ODataId

Steps to reproduce

using Pulumi.AzureAD;

      var appName = testaks;
      var adApp = new Application(appName, new ApplicationArgs()
      {
        DisplayName = appName,
      });

Expected: create an AzureAD application
Actual: * Could not create application: json.Marshal(): json: error calling MarshalJSON for type msgraph.Application: json: error calling MarshalJSON for type *msgraph.Owners: marshaling Owners: encountered DirectoryObject with nil ODataId

[stazz]

Pending for new release of TF provider, the issue already has PR: hashicorp/terraform-provider-azuread#588 .