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
I updated the modules to the 1.9.2 version, only creating a new connected organization with a sponsor is possible with the command New-MgEntitlementManagementConnectedOrganization, and the same errors persist with the rest of commands. (look below for error messages)
step to reproduce
connexion to azure AD with access token
Select-MgProfile -Name "beta"
Connect-MgGraph -Scopes "EntitlementManagement.ReadWrite.All"
...
[.. ] check if domain is AzureAD tenant or One time pass-code
... if One time pass-code domain :
$DomainName = "test0001.com"
$IdentitySources = @{
"@odata.type" = "#microsoft.graph.domainIdentitySource"
domainName = "$DomainName"
displayName = "$DomainName"
}
$AzureADUserSponsor = @{
id = "{User_GUID}"
"@Odata.id" = "https://graph.microsoft.com/beta/users/{User_GUID}"
}
New-MgEntitlementManagementConnectedOrganization -DisplayName "test0001.com" -Description "desc0001" -IdentitySources $IdentitySources -internalSponsors $AzureADUserSponsor
Update-MgEntitlementManagementConnectedOrganization -ConnectedOrganizationId {Org_Id} -Description "desc0002" -IdentitySources $IdentitySources -DisplayName "test0002.com" -internalSponsors $AzureADUserSponsor
Update-MgEntitlementManagementConnectedOrganization : **The model is invalid**.
Au caractère Ligne:1 : 1
+ Update-MgEntitlementManagementConnectedOrganization -ConnectedOrganiz ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation : ({ ConnectedOrga...Organization1 }:<>f__AnonymousType84`2) [Update-MgEntitl..._UpdateExpanded], RestException`1
+ FullyQualifiedErrorId : InvalidModel,Microsoft.Graph.PowerShell.Cmdlets.UpdateMgEntitlementManagementConnectedOrganization_UpdateExpanded
New-MgEntitlementManagementConnectedOrganizationInternalSponsor -ConnectedOrganizationId {GUID_of_Other_org} -Id {User_Guid}
New-MgEntitlementManagementConnectedOrganizationInternalSponsor : **No HTTP resource was found that matches the request URI
'https://igaelm-asev3-pdsapi-neu.igaelm-asev3-environment-neu.p.azurewebsites.net/api/v1/connectedOrganizations('7933ca34-7eb3-4d39-9f5f-bf92a4fb30c6')/internalSponsors'.**
Au caractère Ligne:1 : 1
+ New-MgEntitlementManagementConnectedOrganizationInternalSponsor -Conn ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation : ({ ConnectedOrga...rectoryObject }:<>f__AnonymousType84`2) [New-MgEntitleme..._CreateExpanded], RestException`1
+ FullyQualifiedErrorId : Microsoft.Graph.PowerShell.Cmdlets.NewMgEntitlementManagementConnectedOrganizationInternalSponsor_CreateExpanded
related bugs
The command get-MgEntitlementManagementConnectedOrganization return a null value on internal/external sponsor even if the sponsor exist on the ConnectedOrganization.
=> behaviors not seen on graph API explorer.
The API does not support managing internal/external sponsors by updating a connectedOrganization; thus, The model is invalid error message when using Update-MgEntitlementManagementConnectedOrganization -ConnectedOrganizationId {Org_Id} -Description "desc0002" -IdentitySources $IdentitySources -DisplayName "test0002.com" -internalSponsors $AzureADUserSponsor. See https://docs.microsoft.com/en-us/graph/api/connectedorganization-update?view=graph-rest-1.0&tabs=http#request-body for properties that can be updated. Unfortunately, the metadata (that the SDK is generated from) is not currently fully annotated to tell us which properties are updatable, so we don't generate parameters for them.
New-MgEntitlementManagementConnectedOrganizationInternalSponsor is not the correct command to add an internal sponsor to a connected organization and should not be generated. The correct command, New-MgEntitlementManagementConnectedOrganizationInternalSponsorByRef, is currently missing and will be added to the SDK as part of the next release.
Please use the List, Add, and Remove APIs to manage external/internal sponsors, as shown in the linked API reference docs.
Uh oh!
There was an error while loading. Please reload this page.
Description
With 1.9.1 version of the Microsoft.Graph.Identity.* modules, it was impossible to manage the internal / external sponsor with the following commands:
I updated the modules to the 1.9.2 version, only creating a new connected organization with a sponsor is possible with the command New-MgEntitlementManagementConnectedOrganization, and the same errors persist with the rest of commands. (look below for error messages)
step to reproduce
related bugs
=> behaviors not seen on graph API explorer.
actual modules version
The text was updated successfully, but these errors were encountered: