Owner is sufficient for the role assignment, but it does not satisfy MFA. RequestDisallowedByAzure means the user token Azure DevOps used for automatic setup did not contain a valid MFA claim.
Sign out of Azure DevOps and Azure, open a private browser session, sign in again, complete MFA, and retry. If Owner is eligible through PIM, reactivate it and complete MFA during activation. Your Entra administrator can confirm the request in the sign-in logs. Do not create an MFA exclusion; Azure's mandatory enforcement can ignore such exclusions for resource-management writes.
If automatic creation still fails, use a workload identity federation service connection. Have an authenticated administrator create an app registration or user-assigned managed identity, grant it the required Azure role at the narrowest scope, add the federated credential generated by Azure DevOps, then save and verify the connection. This avoids stored secrets and leaves MFA on human administrative actions.