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
VERBOSE: []: [[AADAdministrativeUnit]AADAdministrativeUnit-xxxx] Creating an Azure AD Administrative Unit with DisplayName {xxxx}
VERBOSE: []: [[AADAdministrativeUnit]AADAdministrativeUnit-xxxx] Creating new Administrative Unit with: description=xyz.
displayName=xyz
VERBOSE: []: [[AADAdministrativeUnit]AADAdministrativeUnit-xxxx] POST https://graph.microsoft.com/beta/administrativeUnits with 119-byte payload
VERBOSE: []: [[AADAdministrativeUnit]AADAdministrativeUnit-xxxx] received 393-byte response of content type application/json
VERBOSE: []: [[AADAdministrativeUnit]AADAdministrativeUnit-xxxx] Adding new dynamic member {id}
##[error][Request_BadRequest] : An unexpected instance annotation name 'https://graph.microsoft.com/beta/administrativeUnits' was found when reading from the JSON reader, In OData, Instance annotation name must start with @.##[error]PowerShell exited with code '1'.
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered:
Description of the issue
When trying to deploy an AADAdministrativeUnit we get the following:
An unexpected instance annotation name 'https://graph.microsoft.com/beta/administrativeUnits' was found when reading from the JSON reader, In OData, Instance annotation name must start with @.
Microsoft 365 DSC Version
1.24.221.1
Which workloads are affected
Azure Active Directory
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: