Creating Workspace in DevOps with SPN leaves workspace inaccessible

I have created an ARM Template/Parameter files that deploys the workspace. After deploying using an SPN in DevOps, I get the error: "You need permission to access workspace" when trying to access the workspace. I am configured as the Active Directory Admin on the resource, and owner of the resource in Access Control. Firewall rules allows all IP addresses.

Using the same exact ARM Template/Parameter files, but deploying using the Azure Portal leaves the workspace in the correct state. I am able to access the studio as expected.

The SPN that deploys the ARM template has been granted the Subscription Owner role.

I can not detect any difference in what has been deployed.

Is there a known issue with deploying Synapse with DevOps / SPN?

Start by reproducing the Synapse workspace deployment with the supplied ARM template and parameter files through DevOps using the service principal, then compare it with the Azure Portal deployment. Investigate the resulting workspace permissions and access configuration; done means the service-principal deployment leaves the workspace accessible to the configured administrator.

Written by the indexing model from the issue text.