Access 'Verifiable Credential' on azure portal

Question

Access 'Verifiable Credential' on azure portal

山口 31

I'm trying to set up verifiable credential as described in the following article:

https://learn.microsoft.com/en-us/azure/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant#set-up-verifiable-credentials

I set up a service principal, a key vault, and application, then navigating to 'Verifiable Credential' page shows the error
'Your organization is not yet set up to issue Verifiable Credentials, please navigate to the "Getting started" item on the left menu. '

I navigated to "Getting started", but it didn't work and generated same error message.

What should i do to access 'Verifiable Credential' page?

In the above article "Prerequisites" are:

If you don't have Azure subscription, create one for free.
Sign up for Azure Active Directory Premium editions subscription in your tenant.
Ensure that you have the global administrator permission for the directory you want to configure.
Ensure that you have PowerShell 7.0.6 LTS-x64, PowerShell 7.1.3-x64, or later installed.

I think i have met these "Prerequisites", i.e. I have Azure subscription, Azure Active Directory P2 license, and "global administrator permission"

Juan Camilo Ruiz (Microsoft) 101 Reputation points Microsoft Employee

2022-02-15T22:30:07.823+00:00
Hello there,

Let's try to check a couple of things on your setup, seems that something might be missing.

Go to the KeyVault (that you going to be using with the VC service, in there go to Access Policies: there should be 2 service principals Verify Credentials Issuer service and Verified Credentials Request service. Both service principals should have:

Key Permissions get and sign

Secret Permissions get.

Your user which is the admin should also have these permissions

Under the App Registration, select the App name that you use for the Issuer service and check the API permissions

Check that you have correctly assign the Admin consent for the Request Service createAll permission name as shown in this picture
Juan Camilo Ruiz (Microsoft) 101 Reputation points Microsoft Employee

2022-02-16T00:18:17.307+00:00

The team has confirmed that an issue was found as a consequence of a recent change that was deployed in production. The fix for the issue is on its way, we will update this thread once it is fully deployed. Really sorry for the inconvenience and thanks for reporting the issue.

Juan C

Accepted answer

1 additional answer

Your answer

Juan Camilo Ruiz (Microsoft) 101 Reputation points Microsoft Employee

2022-02-15T22:30:07.823+00:00

Hello there,

Let's try to check a couple of things on your setup, seems that something might be missing.

Go to the KeyVault (that you going to be using with the VC service, in there go to Access Policies: there should be 2 service principals Verify Credentials Issuer service and Verified Credentials Request service. Both service principals should have:

Key Permissions get and sign

Secret Permissions get.

Your user which is the admin should also have these permissions

Under the App Registration, select the App name that you use for the Issuer service and check the API permissions

Check that you have correctly assign the Admin consent for the Request Service createAll permission name as shown in this picture
Juan Camilo Ruiz (Microsoft) 101 Reputation points Microsoft Employee

2022-02-16T00:18:17.307+00:00

The team has confirmed that an issue was found as a consequence of a recent change that was deployed in production. The fix for the issue is on its way, we will update this thread once it is fully deployed. Really sorry for the inconvenience and thanks for reporting the issue.

Juan C

Answer 1

Siva-kumar-selvaraj 15,721

Hi @山口 ,

Thanks for reaching out and apologies for the inconvenience caused by above issue.

As @Juan Camilo Ruiz (Microsoft) mentioned, our engineering team has verified that a problem was discovered as a result of a recent production modification. We are working on resolving the issue and will update this thread once it is fully implemented.

Thank you for your time and patience throughout this issue.

山口 31 Reputation points

2022-02-16T05:02:29.073+00:00

Hi @sikumars-msft, @Juan Camilo Ruiz (Microsoft) ,

Thank you for your reply.
I'll waiting for the issue to be solved.

Answer 2

Juan Camilo Ruiz (Microsoft) 101 Microsoft Employee

I'm happy to share that the fix for the issue has been rolled out. @山口 you should be able to complete the setup of the VC service. Please let us know if you have any issues.

cc @sikumars-msft

山口 31 Reputation points

2022-02-18T08:18:39.64+00:00

@Juan Camilo Ruiz (Microsoft) @sikumars-msft

I have issued VC successfully on Azure portal.
Thank you!!

Share via

Access 'Verifiable Credential' on azure portal

1 additional answer

Your answer