@Davidson_Silva this happened due to an incorrect service principal(enterprise application) on the Azure end. First, create an Azure sp with application ID “e90a1407-55c3-432d-9cb1-3638900a9d22” and used its id in the role assignment’s principal_id
1 Like