Skip to content

Commit 2d17507

Browse files
authored
Merge pull request #96929 from bolt-io/patch-20
Update to reflect service renaming
2 parents 422f178 + d0fdbf6 commit 2d17507

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Tutorial - Configure your tenant for Microsoft Entra Verified ID
3-
description: In this tutorial, you learn how to configure your tenant to support the Verifiable Credentials service.
3+
description: In this tutorial, you learn how to configure your tenant to support the Verified ID service.
44
ms.service: decentralized-identity
55
ms.subservice: verifiable-credentials
66
author: barclayn
@@ -24,7 +24,7 @@ Specifically, you learn how to:
2424

2525
> [!div class="checklist"]
2626
> - Create an Azure Key Vault instance.
27-
> - Set up the Verifiable Credentials service.
27+
> - Set up the Verified ID service.
2828
> - Register an application in Azure AD.
2929
3030
The following diagram illustrates the Verified ID architecture and the component you configure.
@@ -77,6 +77,7 @@ The Verifiable credentials service request is the Request Service API, and it ne
7777

7878
1. To save the changes, select **Add**.
7979

80+
8081
## Set up Verified ID
8182

8283
To set up Verified ID, follow these steps:
@@ -87,7 +88,7 @@ To set up Verified ID, follow these steps:
8788

8889
1. Set up your organization by providing the following information:
8990

90-
1. **Organization name**: Enter a name to reference your business within Verifiable Credentials. Your customers don't see this name.
91+
1. **Organization name**: Enter a name to reference your business within Verified IDs. Your customers don't see this name.
9192

9293
1. **Domain**: Enter a domain that's added to a service endpoint in your decentralized identity (DID) document. The domain is what binds your DID to something tangible that the user might know about your business. Microsoft Authenticator and other digital wallets use this information to validate that your DID is linked to your domain. If the wallet can verify the DID, it displays a verified symbol. If the wallet can't verify the DID, it informs the user that the credential was issued by an organization it couldn't validate.
9394

@@ -99,7 +100,7 @@ To set up Verified ID, follow these steps:
99100
1. Under **Advanced**, you may choose the **trust system** that you want to use for your tenant. You can choose from either **Web** or **ION**. Web means your tenant uses [did:web](https://w3c-ccg.github.io/did-method-web/) as the did method and ION means it uses [did:ion](https://identity.foundation/ion/).
100101

101102
>[!IMPORTANT]
102-
> The only way to change the trust system is to opt-out of verifiable credentials and redo the onboarding.
103+
> The only way to change the trust system is to opt-out of the Verified ID service and redo the onboarding.
103104
104105

105106
1. Select **Save and get started**.
@@ -156,7 +157,8 @@ You can choose to grant issuance and presentation permissions separately if you
156157

157158
## Service endpoint configuration
158159

159-
1. Navigate to the Verified ID in the Azure portal.
160+
161+
1. Navigate to the Verified ID service in the Azure portal.
160162
1. Select **Registration**.
161163
1. Notice that there are two sections:
162164
1. Website ID registration

0 commit comments

Comments
 (0)