This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 57.99999999999999%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDK%3C/text%3E%3C/svg%3E)
After running the starter kit, I cannot access the Purview Studio. I'm logged in as the user given to the script and I'm still denied access. How do I find what user is assigned the role that can first login?
Hello @Dan Kellett ,
Thanks for brining this to our attention.
We are reaching out to the internal team to get this fixed. I will be update you once I hear back from the team.
Hi @Dan Kellett - Can you please navigate to Resource Group (the resource group in which the demo environment was deployed to), click "Deployments", and confirm if the deployment status is equal to Succeeded. It sounds as though the deployment may not have run completely as the Service Principal used for the post deployment script is intended to add the executing user to an Azure Purview role.
Thanks for the help. The deployments were OK. I think this was related to the new AD user I had created using an alias on my Microsoft account. I've run the scripts again and simply entered the service principal user and things are working fine now.
I had created a user using an alias on my Microsoft account "hotmail.com vs outlook.com" that was likely causing authentication issues. I've re-run the script and entered the service principal user and things are working fine now.
Thanks!
Hello @Dan Kellett ,
Glad to know that your issue has resolved. And thanks for sharing the solution, which might be beneficial to other community members reading this thread.