Hi,
I am trying to automate a CI/CD pipeline in Gitlab (after successfully doing this in AzureDevOps and seeing it is possible with Microsoft tooling in Github). In support of this, I had planned to use the PAC CLI (1.9.4). When trying the pac auth create command from PowerShell on a workgroup VM, it works when I do not specify anything beyond the URL and fill in a pop-up window with my domain user account, but it does not work when I try to use an AppId/ClientSecret/TenantId. This same AppId/ClientSecret/TenantId combo works from an Azure DevOps Pipeline also setup in a local workgroup. The issue might be due to us operating in a GCC High environment, but it is not clear to me. I cannot use a User/Pwd combo since we enforce MFA.
The command I issue is:
pac auth create --name CAS-PoC-SB01-Acct --url https://orgXXXX.crm.microsoftdynamics.us --applicationId XXXX --clientSecret XXXX --tenant XXXX --cloud UsGovHigh
This results in:
Microsoft PowerPlatform CLI
Version: 1.9.4+gbda9f20
Error: AADSTS900382: Confidential Client is not supported in Cross Cloud request.
Is this a defect or has anyone else successfully used the AppId/ClientSecret/TenantId flags in a GCC High environment from the PAC CLI? Are there any suggestions for alternative approaches if this is not supported? The goal is to be able to re-create the CI/CD pipeline capabilities present in Gitlab/Azure DevOps Pipelines using any generic Pipeline tooling that supports CLI jobs.
