Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14023

Missing Step in Azure KMS Doc - URI /security-azure-kms/#prerequisites

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Last comment by Customer:
      true
    • Story Points:
      1
    • Sprint:
      DevEd Q4S3 Canyonlands 12/1

      Description

      Description

      Description

      In the Prerequisite portion of our documentation it states the following:

      Have the Resource Group name for an Azure Resource Group in which the Azure Application has the :guilabel: Azure Key Vault Reader (Preview) role.

      Customer suggested the following since they didn't realize they needed an Active Directory role assigned:

      • Have the Resource Group name for an Azure Resource Group containing the Key Vault
      • Have an Active Directory Application with the role of "Azure Key Vault Reader (Preview)" assigned to it

      Let me know if this is something that can be addressed as a user came into intercom and the wording wasn't clear enough for them to understand what they were missing when they we receiving a Vault Key mismatch error.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Activity

            People

            Assignee:
            nathan.leniz Nathan Leniz
            Reporter:
            valentina.jukic Valentina Jukic
            Participants:
            Last commenter:
            Steven Vannelli Steven Vannelli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              47 weeks, 6 days ago