You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For long running operations, such as creating an external connection schema, we need to return the location header which allows users to check the operation state. Right now, we don’t return any information which makes it impossible for users to check the operation status, because the link to check the operation state is returned only once and there’s no other way to construct or retrieve it.
With the latest release the response headers have been deserialized and can the individual header params can be accessed via a hashtable.
In this case one can retrieve the location header.
For long running operations, such as creating an external connection schema, we need to return the location header which allows users to check the operation state. Right now, we don’t return any information which makes it impossible for users to check the operation status, because the link to check the operation state is returned only once and there’s no other way to construct or retrieve it.
In the PowerShell SDK the current recommendation is to use Invoke-MgGraphRequest microsoftgraph/msgraph-sdk-powershell#1452
The text was updated successfully, but these errors were encountered: