Merge pull request #273961 from mehasharma/quickstart-updates

adding changes to quickstart

Author: v-dirichards

articles/trusted-signing/faq.yml

@@ -116,7 +116,10 @@ sections:
           Trusted Signing will suspend accounts and or revoke signing certificates if the certificate is found to be misused or abused per our service's Terms of Use. We engage with you directly in such cases following the Code Signing Baseline Requirements (CSBRs) guidelines. 
       - question: What if I get Azure.Identity.CredentialUnavailableException?
         answer: |
-          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.
+          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're outside of Azure.
+      - question: What if I change the Subscription ID or Tenant ID?
+        answer: |
+         At the moment, Trusted Signing resources can't 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.
   
 ##additionalContent: |
-    ## Next steps
+    ## Next steps

articles/trusted-signing/quickstart.md

@@ -52,7 +52,7 @@ A resource provider is a service that supplies Azure resources. Use the Azure po
 
 2. To finish the authentication process, follow the steps displayed in your terminal. For other sign-in options, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
 
-3. When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see Use extensions with the [Azure CLI](/cli/azure/azure-cli-extensions-overview).
+3. When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see Use extensions with the [Azure CLI](/cli/azure/azure-cli-extensions-overview). Additional information for Trusted Signing CLI extension is available at [Trusted Signing Service](https://learn.microsoft.com/cli/azure/service-page/trusted%20signing%20service?view=azure-cli-latest)
 
 4. To see the versions of Azure CLI and dependent libraries that are installed, use the `az version` command.
 •   To upgrade to the latest version, use the following command:
@@ -122,8 +122,8 @@ The resources must be created in Azure regions where Trusted Signing is currentl
 
 - Between 3-24 alphanumeric characters.
 - Begin with a letter, end with a letter or digit, and not contain consecutive hyphens.
-- Globally unique.
 - Case insensitive (“Abc” is the same as “abc”).
+- Account names beginning with "one" are rejected by ARM.
 
 # [Azure CLI](#tab/account-cli)
 
@@ -167,8 +167,8 @@ trustedsigning create -n MyAccount -l eastus -g MyResourceGroup --sku Premium
 
 - Between 3-24 alphanumeric characters.
 - Begin with a letter, end with a letter or digit, and not contain consecutive hyphens.
-- Globally unique.
 - Case insensitive (“Abc” is the same as “abc”).
+- Account names beginning with "one" are rejected by ARM.
 
 **Helpful commands**:
 
@@ -211,6 +211,11 @@ Here are the steps to create an Identity Validation request:
 6. **Certificate subject preview**:  The preview provides a snapshot of the information displayed in the certificate.
 7. **Review and accept Trusted Signing Terms of Use**.  Terms of Use can be downloaded for review.  
 8. Select the **Create** button.
+9. Upon successful creation of the request, the Identity Validation request status changes to "In Progress".
+10. If Additional documents are required, an email is sent and the request status changes to "Action Required".
+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.
+    1. "Completed": When process is completed successfully.
+    1. "Failed": When the process is not completed successfully. 
 
 :::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":::
 
@@ -220,7 +225,7 @@ Here are the steps to create an Identity Validation request:
 
 | Requirements         | Details     |
 | :------------------- | :------------------- |
-| Onboarding           | Trusted Signing at this time can only onboard Legal Business Entities that have verifiable tax history of three or more years. |
+| Onboarding           | Trusted Signing at this time can only onboard Legal Business Entities that have verifiable tax history of three or more years. For a quicker onboarding process ensure public records for the Legal Entity being validated are upto date. |
 | Accuracy             | Ensure you provide the correct information for Public Identity Validation. Any changes or typos require you to complete a new Identity Validation request and affect the associated certificates used for signing.|
 | Additional documentation            | You are notified though email, if we need extra documentation to process the identity validation request. The documents can be uploaded in Azure portal. The email contains information about the file size requirements. Ensure the documents provided are latest.|
 | Failed email verification            | You are required to initiate a new Identity Validation request if email verification fails.|