Skip to content

Commit 766087b

Browse files
adding changes to quickstart
1 parent 1bab9f9 commit 766087b

File tree

2 files changed

+10
-2
lines changed

2 files changed

+10
-2
lines changed

articles/trusted-signing/faq.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -117,6 +117,9 @@ sections:
117117
- question: What if I get Azure.Identity.CredentialUnavailableException?
118118
answer: |
119119
You should expect to see this error on environments outside of Azure [see here](https://github.com/Azure/azure-sdk-for-net/issues/29471). Recommendation is to "exclude ManagedIdentity" if you are outside of Azure.
120+
- question: What if I change the Subscription ID or Tenant ID?
121+
answer: |
122+
At the moment, Trusted Signing resources cannot be migrated across Subscriptions or Tenants. Hence, any change to Tenant ID or Subscription ID will need fro you to create all the Trusted Signing resources again.
120123
121124
##additionalContent: |
122125
## Next steps

articles/trusted-signing/quickstart.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -122,8 +122,8 @@ The resources must be created in Azure regions where Trusted Signing is currentl
122122

123123
- Between 3-24 alphanumeric characters.
124124
- Begin with a letter, end with a letter or digit, and not contain consecutive hyphens.
125-
- Globally unique.
126125
- Case insensitive (“Abc” is the same as “abc”).
126+
- Account names beginning with "one" are rejected by ARM.
127127

128128
# [Azure CLI](#tab/account-cli)
129129

@@ -167,8 +167,8 @@ trustedsigning create -n MyAccount -l eastus -g MyResourceGroup --sku Premium
167167

168168
- Between 3-24 alphanumeric characters.
169169
- Begin with a letter, end with a letter or digit, and not contain consecutive hyphens.
170-
- Globally unique.
171170
- Case insensitive (“Abc” is the same as “abc”).
171+
- Account names beginning with "one" are rejected by ARM.
172172

173173
**Helpful commands**:
174174

@@ -211,6 +211,11 @@ Here are the steps to create an Identity Validation request:
211211
6. **Certificate subject preview**: The preview provides a snapshot of the information displayed in the certificate.
212212
7. **Review and accept Trusted Signing Terms of Use**. Terms of Use can be downloaded for review.
213213
8. Select the **Create** button.
214+
9. Upon successful creation of the request, the Identity Validation request status changes to "In Progress".
215+
10. If Additional documents are required, an email is sent and the request status changes to "Action Required".
216+
11. Once the identity validation process is complete, the request status will change, and an email is sent with the updated status of the request.
217+
a. "Completed": When process is completed successfully.
218+
b. "Failed": When the process is not completed successfully.
214219

215220
:::image type="content" source="media/trusted-signing-identity-validation-public.png" alt-text="Screenshot of trusted-signing-identityvalidation-public." lightbox="media/trusted-signing-identity-validation-public.png":::
216221

0 commit comments

Comments
 (0)