Merge pull request #46771 from prashanthyv/master

Update the document to not include

Author: GitHubber17

articles/key-vault/key-vault-get-started.md

@@ -25,9 +25,6 @@ This article helps you get started with Azure Key Vault using PowerShell and wal
 
 Azure Key Vault is available in most regions. For more information, see the [Key Vault pricing page](https://azure.microsoft.com/pricing/details/key-vault/).
 
-> [!NOTE]
-> This article does not include instructions on how to write an Azure application. You can use the [Azure Key Vault sample application](https://www.microsoft.com/download/details.aspx?id=45343) for these steps.
-
 For Cross-Platform Command-Line Interface instructions, see [this equivalent tutorial](key-vault-manage-with-cli2.md).
 
 ## Requirements
@@ -266,7 +263,7 @@ To change the authorization of an application to use keys or secrets:
 ## <a id="HSM"></a>Working with a hardware security module (HSM)
 For added assurance, you can import or generate keys in hardware security modules (HSMs) that never leave the HSM boundary. The HSMs are FIPS 140-2 Level 2 validated. If this requirement doesn't apply to you, skip this section and go to [Delete the key vault and associated keys and secrets](#delete).
 
-To create these HSM-protected keys, you must use the [Azure Key Vault Premium service tier to support HSM-protected keys](https://azure.microsoft.com/pricing/free-trial/). In addition, note that this functionality is not available for Azure China.
+To create these HSM-protected keys, you must use the [Azure Key Vault Premium service tier to support HSM-protected keys](https://azure.microsoft.com/pricing/details/key-vault/). In addition, note that this functionality is not available for Azure China.
 
 When you create the key vault, add the **-SKU** parameter:
 

articles/key-vault/key-vault-overview.md

@@ -26,13 +26,12 @@ You have passwords, connection strings, and other pieces of information that are
 
 Key Vault allows you to create multiple secure containers, called vaults. These vaults are backed by hardware security modules (HSMs). Vaults help reduce the chances of accidental loss of security information by centralizing the storage of application secrets. Key Vaults also control and log the access to anything stored in them. Azure Key Vault can handle requesting and renewing Transport Layer Security (TLS) certificates, providing the features required for a robust certificate lifecycle management solution.
 
- Azure Key vault is designed to support application keys and secrets. Key Vault is not intended to be used as a store for user passwords.
-
+ Azure Key vault is designed to support any type of secret. By this we mean Key Vault can be used to store passwords, database credentials, API keys and, certificates, which can be either software protected or HSM protected
 ## Why use Azure Key Vault?
 
 ### Centralize application secrets
 
-Centralizing storage of application secrets in Azure Key Vault allows you to control their distribution. This greatly reduces the chances that secrets may be accidentally leaked. When using Key Vault, application developers no longer need to store security information in their application. This eliminates the need to make this information part of the code. For example, an application may need to connect to a database. Instead of storing the connection string in the app codes, store it securely in Key Vault.
+Centralizing storage of application secrets in Azure Key Vault allows you to control their distribution. Key Vault greatly reduces the chances that secrets may be accidentally leaked. When using Key Vault, application developers no longer need to store security information in their application. This eliminates the need to make this information part of the code. For example, an application may need to connect to a database. Instead of storing the connection string in the app codes, store it securely in Key Vault.
 
 Your applications can securely access the information they need by using URIs that allow them to retrieve specific versions of a secret after the application’s key or secret is stored in Azure Key Vault. This happens without having to write custom code to protect any of the secret information.
 
@@ -50,7 +49,7 @@ Finally, Azure Key Vault is designed so that Microsoft does not see or extract y
 
 ### Monitor access and use
 
-Once that you have created a couple of Key Vaults you will want to monitor how and when your keys and secrets are being accessed. You can do this by enabling logging for Key Vault. You can configure Azure Key Vault to:
+Once you have created a couple of Key Vaults, you will want to monitor how and when your keys and secrets are being accessed. You can do this by enabling logging for Key Vault. You can configure Azure Key Vault to:
 
 - Archive to a storage account.
 - Stream to an event hub.
@@ -62,19 +61,19 @@ You have control over your logs and you may secure them by restricting access an
 
 When storing valuable data, you must take several steps. Security information must be secured, it must follow a lifecycle, it must be highly available. Azure Key Vault simplifies a lot of this by:
 
-- Removing the need for in-house knowledge of HSMs.
+- Removing the need for in-house knowledge of Hardware Security Modules
 - Scaling up on short notice to meet your organization’s usage spikes.
-- Replicating the contents of your Key Vault within a region and to a secondary region. This ensures high availability and takes away the need of any action from the administrator to trigger the fail over.
+- Replicating the contents of your Key Vault within a region and to a secondary region. Key Vault ensures high availability and takes away the need of any action from the administrator to trigger the failover.
 - Providing standards Azure administration options via the portal, Azure CLI and PowerShell.
 - Automating certain tasks on certificates that you purchase from Public CAs, such as enroll and renew.
 
 In addition, Azure Key Vaults allow you to segregate application secrets. Applications may access only the vault that they are allowed to access, and they be limited to only perform specific operations. You can create an Azure Key Vault per application and restrict the secrets stored in a Key Vault to a specific application and team of developers.
 
 ### Integrate with other Azure services
 
-As a secure store in Azure, Key Vault has been used to simplify scenarios like [Azure Disk Encryption](../security/azure-security-disk-encryption.md), the [always encrypted]( https://docs.microsoft.com/sql/relational-databases/security/encryption/always-encrypted-database-engine) functionality in SQL server and Azure SQL, [Azure web apps]( https://docs.microsoft.com/azure/app-service/web-sites-purchase-ssl-web-site). Key Vault itself can integrate with storage accounts, event hubs and log analytics.
+As a secure store in Azure, Key Vault has been used to simplify scenarios like [Azure Disk Encryption](../security/azure-security-disk-encryption.md), the [always encrypted]( https://docs.microsoft.com/sql/relational-databases/security/encryption/always-encrypted-database-engine) functionality in SQL server and Azure SQL, [Azure web apps]( https://docs.microsoft.com/azure/app-service/web-sites-purchase-ssl-web-site). Key Vault itself can integrate with storage accounts, event hubs, and log analytics.
 
 ## Next steps
 
 - [Quickstart: Create an Azure Key Vault using the CLI](quick-create-cli.md)
-- [Configure an Azure web application to read a secret from Key vault](tutorial-web-application-keyvault.md)
+- [Configure an Azure web application to read a secret from Key vault](tutorial-web-application-keyvault.md)

articles/key-vault/quick-create-net.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Quickstart - Configure an Azure web application to set and retrieve a secret from Key vault | Microsoft Docs
-description: Quickstart showing how to configure an ASP.Net core application to set and retrieve a secret from Key vault
+title: Quickstart- Set and retrieve a secret from Azure Key Vault using a Node Web App | Microsoft Docs
+description: Quickstart- Set and retrieve a secret from Azure Key Vault using a Node Web App 
 services: key-vault
 author: prashanthyv
 manager: sumedhb
@@ -25,7 +25,7 @@ In this quickstart, you go over the necessary steps for getting an Azure web app
 > * [Enable managed service identities](../active-directory/managed-service-identity/overview.md).
 > * Grant the required permissions for the web application to read data from Key vault.
 
-Before we go any further, read the [basic concepts](key-vault-whatis.md#basic-concepts) especially [Managed Service Identity](../active-directory/managed-service-identity/overview.md)
+Before we go any further, please read the [basic concepts](key-vault-whatis.md#basic-concepts).
 
 ## Prerequisites
 

articles/key-vault/quick-create-node.md

@@ -1,6 +1,6 @@
 ---
-title: Azure quickstart - Set and retrieve a secret from Azure Key Vault using a Node Web App | Microsoft Docs
-description: In this quickstart you configure an Node.js application to set and retrieve a secret from Key vault
+title: Quickstart- Set and retrieve a secret from Azure Key Vault using a Node Web App | Microsoft Docs
+description: Quickstart- Set and retrieve a secret from Azure Key Vault using a Node Web App 
 services: key-vault
 documentationcenter: 
 author: prashanthyv
@@ -17,7 +17,7 @@ ms.custom: mvc
 
 # Quickstart: Set and retrieve a secret from Azure Key Vault using a Node Web App 
 
-This QuickStart shows how to store a secret in Key Vault and how to retrieve it using a Web app. This web app may be  run locally or in Azure. The quickstart uses Node.js and Managed service identities (MSIs)
+This quickstart shows you how to store a secret in Key Vault and how to retrieve it using a Web app. To see the secret value you would have to run this on Azure. The quickstart uses Node.js and Managed service identities (MSIs)
 
 > [!div class="checklist"]
 > * Create a Key Vault.
@@ -122,8 +122,6 @@ Below are the few steps we need to do
     ```
     # Bash
     az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name <app_name> --runtime "NODE|6.9" --deployment-local-git
-    # PowerShell
-    az --% webapp create --resource-group myResourceGroup --plan myAppServicePlan --name <app_name> --runtime "NODE|6.9"
     ```
     When the web app has been created, the Azure CLI shows output similar to the following example:
     ```
@@ -199,4 +197,4 @@ Make sure that you replaced the name <YourKeyVaultName> with your vault name
 * [Azure Key Vault Home Page](https://azure.microsoft.com/services/key-vault/)
 * [Azure Key Vault Documentation](https://docs.microsoft.com/azure/key-vault/)
 * [Azure SDK For Node](https://docs.microsoft.com/javascript/api/overview/azure/key-vault)
-* [Azure REST API Reference](https://docs.microsoft.com/rest/api/keyvault/)
+* [Azure REST API Reference](https://docs.microsoft.com/rest/api/keyvault/)

articles/key-vault/toc.yml

@@ -42,6 +42,15 @@
     href: key-vault-ovw-storage-keys.md
   - name: Throttling
     href: key-vault-ovw-throttling.md
+  - name: About keys, secrets and certificates
+    href: about-keys-secrets-and-certificates.md
+    items:
+    - name: Get started with certificates
+      href: certificate-scenarios.md
+    - name: Certificate creation methods
+      href: create-certificate.md
+    - name: Monitor and manage certificate creation
+      href: create-certificate-scenarios.md
 - name: How-to guides
   items:
   - name: Azure Key Vault logging
@@ -110,34 +119,19 @@
   items:
   - name: Service overview
     href: https://azure.microsoft.com/services/key-vault/
-  - name: About keys, secrets and certificates
-    href: about-keys-secrets-and-certificates.md
-    items:
-    - name: Get started with certificates
-      href: certificate-scenarios.md
-    - name: Certificate creation methods
-      href: create-certificate.md
-    - name: Monitor and manage certificate creation
-      href: create-certificate-scenarios.md
   - name: Authentication, requests and responses
     href: authentication-requests-and-responses.md
-  - name: Customer data features
+  - name: Customer Data 
     href: key-vault-customer-data.md
   - name: Common parameters and headers
     href: common-parameters-and-headers.md
-  - name: Key Vault versions
+  - name: Release Notes
     href: key-vault-versions.md
-  - name: Azure roadmap
-    href: https://azure.microsoft.com/roadmap/?category=security-identity
-  - name: Blog
+  - name: Azure Key Vault Blog
     href: http://blogs.technet.com/b/kv/
-  - name: Code samples
-    href: https://github.com/Azure-Samples?utf8=%E2%9C%93&q=key+vault&type=&language=
-  - name: Forums
-    href: https://social.msdn.microsoft.com/forums/azure/home?forum=AzureKeyVault
   - name: Pricing
     href: https://azure.microsoft.com/pricing/details/key-vault/
-  - name: Pricing calculator
+  - name: Pricing Calculator
     href: https://azure.microsoft.com/pricing/calculator/
-  - name: Product feedback
+  - name: Product Feedback
     href: https://feedback.azure.com/forums/906355-azure-key-vault