Merge pull request #109596 from PatAltimore/patricka-blockchain-guidance

v-shils · web-flow · commit 1b0a18d2b792 · 2020-04-01T09:55:22.000-07:00
Add guidance to blockchain articles
diff --git a/articles/blockchain/service/create-member-cli.md b/articles/blockchain/service/create-member-cli.md
@@ -1,7 +1,7 @@
 ---
 title: Create an Azure Blockchain Service member - Azure CLI
 description: Create an Azure Blockchain Service member for a blockchain consortium using the Azure CLI.
-ms.date: 03/12/2020
+ms.date: 03/30/2020
 ms.topic: quickstart
 ms.reviewer: ravastra
 #Customer intent: As a network operator, I want use Azure Blockchain Service so that I can create a blockchain member on Azure
@@ -54,7 +54,7 @@ az resource create \
 | **password** | The password for the member's default transaction node. Use the password for basic authentication when connecting to blockchain member's default transaction node public endpoint.
 | **consortium** | Name of the consortium to join or create. For more information on consortia, see [Azure Blockchain Service consortium](consortium.md).
 | **consortiumAccountPassword** | The consortium account password is also known as the member account password. The member account password is used to encrypt the private key for the Ethereum account that is created for your member. You use the member account and member account password for consortium management.
-| **skuName** | Tier type. Use S0 for Standard and B0 for Basic. Use the *Basic* tier for development, testing, and proof of concepts. Use the *Standard* tier for production grade deployments.
+| **skuName** | Tier type. Use S0 for Standard and B0 for Basic. Use the *Basic* tier for development, testing, and proof of concepts. Use the *Standard* tier for production grade deployments. You should also use the *Standard* tier if you are using Blockchain Data Manager or sending a high volume of private transactions. Changing the pricing tier between basic and standard after member creation is not supported.
 
 It takes about 10 minutes to create the blockchain member and supporting resources.
 
diff --git a/articles/blockchain/service/create-member.md b/articles/blockchain/service/create-member.md
@@ -1,7 +1,7 @@
 ---
 title: Create an Azure Blockchain Service member - Azure portal
 description: Create an Azure Blockchain Service member for a blockchain consortium using the Azure portal.
-ms.date: 03/12/2020
+ms.date: 03/30/2020
 ms.topic: quickstart
 ms.reviewer: ravastra
 #Customer intent: As a network operator, I want use Azure Blockchain Service so that I can create a managed ledger on Azure.
@@ -32,7 +32,7 @@ An Azure Blockchain Service member is a blockchain node in a private consortium
     Consortium | For a new consortium, enter a unique name. If joining a consortium through an invite, choose the consortium you are joining. For more information on consortia, see [Azure Blockchain Service consortium](consortium.md).
     Name | Choose a unique name for the Azure Blockchain Service member. The blockchain member name can only contain lowercase letters and numbers. The first character must be a letter. The value must be between 2 and 20 characters long.
     Member account password | The member account password is used to encrypt the private key for the Ethereum account that is created for your member. You use the member account and member account password for consortium management.
-    Pricing | The node configuration and cost for your new service. Select the **Change** link to choose between **Standard** and **Basic** tiers. Use the *Basic* tier is for development, testing, and proof of concepts. Use the *Standard* tier for production grade deployments.
+    Pricing | The node configuration and cost for your new service. Select the **Change** link to choose between **Standard** and **Basic** tiers. Use the *Basic* tier is for development, testing, and proof of concepts. Use the *Standard* tier for production grade deployments. You should also use the *Standard* tier if you are using Blockchain Data Manager or sending a high volume of private transactions. Changing the pricing tier between basic and standard after member creation is not supported.
     Node password | The password for the member's default transaction node. Use the password for basic authentication when connecting to blockchain member's default transaction node public endpoint.
 
 1. Select **Review + create** to validate your settings. Select **Create** to provision the service. Provisioning takes about 10 minutes.
diff --git a/articles/blockchain/service/data-manager-cli.md b/articles/blockchain/service/data-manager-cli.md
@@ -1,9 +1,9 @@
 ---
 title: Configure Blockchain Data Manager using Azure CLI - Azure Blockchain Service
 description: Create and manage a Blockchain Data Manager for Azure Blockchain Service using Azure CLI
-ms.date: 11/04/2019
+ms.date: 03/30/2020
 ms.topic: article
-ms.reviewer: chroyal
+ms.reviewer: ravastra
 #Customer intent: As a network operator, I want to use Azure CLI to configure Blockchain Data Manager.
 ---
 # Configure Blockchain Data Manager using Azure CLI
@@ -21,7 +21,7 @@ To configure a Blockchain Data Manager instance, you:
 ## Prerequisites
 
 * Install the latest [Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli) and signed in using `az login`.
-* Complete [Quickstart: Use Visual Studio Code to connect to a Azure Blockchain Service consortium network](connect-vscode.md)
+* Complete [Quickstart: Use Visual Studio Code to connect to a Azure Blockchain Service consortium network](connect-vscode.md). Azure Blockchain Service *Standard* tier is recommended when using Blockchain Data Manager.
 * Create an [Event Grid Topic](../../event-grid/custom-event-quickstart-portal.md#create-a-custom-topic)
 * Learn about [Event handlers in Azure Event Grid](../../event-grid/event-handlers.md)
 
diff --git a/articles/blockchain/service/data-manager-portal.md b/articles/blockchain/service/data-manager-portal.md
@@ -1,9 +1,9 @@
 ---
 title: Configure Blockchain Data Manager using Azure portal - Azure Blockchain Service
 description: Create and manage Blockchain Data Manager for Azure Blockchain Service using the Azure portal.
-ms.date: 11/04/2019
+ms.date: 03/30/2020
 ms.topic: article
-ms.reviewer: chroyal
+ms.reviewer: ravastra
 #Customer intent: As a network operator, I want to use the Azure portal to configure Blockchain Data Manager.
 ---
 # Configure Blockchain Data Manager using the Azure portal
@@ -17,7 +17,7 @@ To configure a Blockchain Data Manager instance, you:
 
 ## Prerequisites
 
-* Complete [Quickstart: Create a blockchain member using the Azure portal](create-member.md) or [Quickstart: Create an Azure Blockchain Service blockchain member using Azure CLI](create-member-cli.md)
+* Complete [Quickstart: Create a blockchain member using the Azure portal](create-member.md) or [Quickstart: Create an Azure Blockchain Service blockchain member using Azure CLI](create-member-cli.md). Azure Blockchain Service *Standard* tier is recommended when using Blockchain Data Manager.
 * Create an [Event Grid Topic](../../event-grid/custom-event-quickstart-portal.md#create-a-custom-topic)
 * Learn about [Event handlers in Azure Event Grid](../../event-grid/event-handlers.md)
 
diff --git a/articles/blockchain/service/limits.md b/articles/blockchain/service/limits.md
@@ -1,9 +1,9 @@
 ---
 title: Azure Blockchain Service limits
 description: Overview of the service and functional limits in Azure Blockchain Service
-ms.date: 11/22/2019
+ms.date: 03/30/2020
 ms.topic: conceptual
-ms.reviewer: janders
+ms.reviewer: ravastra
 #Customer intent: As an operator or architect, I want to understand service and functional limits for Azure Blockchain Service.
 ---
 
@@ -13,14 +13,18 @@ Azure Blockchain Service has service and functional limits such as the number of
 
 ## Pricing tier
 
-Maximum limits on transactions and validator nodes depend on whether you provision Azure Blockchain Service at Basic or Standard pricing tiers.
+Maximum limits on transactions and validator nodes depend on whether you provision Azure Blockchain Service at basic or standard pricing tiers.
 
 | Pricing tier | Max transaction nodes | Max validator nodes |
 |:---|:---:|:---:|
 | Basic | 10 | 1 |
 | Standard | 10 | 2 |
 
-Changing the pricing tier between Basic and Standard after member creation is not supported.
+Your consortium network should have a least two Azure Blockchain Service standard tier nodes. Standard tier nodes include two validator nodes. Four validator nodes are required to meet [Istanbul Byzantine Fault Tolerance consensus](https://github.com/jpmorganchase/quorum/wiki/Quorum-Consensus).
+
+Use the basic tier is for development, testing, and proof of concepts. Use the standard tier for production grade deployments. You should also use the *Standard* tier if you are using Blockchain Data Manager or sending a high volume of private transactions.
+
+Changing the pricing tier between basic and standard after member creation is not supported.
 
 ## Storage capacity
 
@@ -46,7 +50,7 @@ Decreasing ledger and log storage size is not supported.
 
 * **Members removed from the consortium cannot be added again**
 
-    Rather, they must be reinvited to join the consortium and create a new member. Their existing member resource are not deleted to preserve historical transactions.
+    Rather, they must be reinvited to join the consortium and create a new member. Their existing member resources are not deleted to preserve historical transactions.
 
 * **All members in a consortium must be using the same ledger version**
 
diff --git a/articles/blockchain/service/overview.md b/articles/blockchain/service/overview.md
@@ -1,7 +1,7 @@
 ---
 title: Azure Blockchain Service overview
 description: Overview of Azure Blockchain Service
-ms.date: 03/12/2020
+ms.date: 03/30/2020
 ms.topic: overview
 ms.reviewer: ravastra
 #Customer intent: As a network operator or developer, I want to understand how I can use Azure Blockchain Service to build and manage consortium blockchain networks on Azure
@@ -15,7 +15,7 @@ Azure Blockchain Service is a fully managed ledger service that enables users th
 * Built-in consortium management
 * Develop smart contracts with familiar development tools
 
-Azure Blockchain Service is designed to support multiple ledger protocols. Currently, it provides support for the Ethereum [Quorum](https://www.goquorum.com/) ledger using the [IBFT](https://github.com/jpmorganchase/quorum/wiki/Quorum-Consensus) consensus mechanism.
+Azure Blockchain Service is designed to support multiple ledger protocols. Currently, it provides support for the Ethereum [Quorum](https://www.goquorum.com/) ledger using the [Istanbul Byzantine Fault Tolerance (IBFT)](https://github.com/jpmorganchase/quorum/wiki/Quorum-Consensus) consensus mechanism.
 
 These capabilities require almost no administration and all are provided at no additional cost. You can focus on app development and business logic rather than allocating time and resources to managing virtual machines and infrastructure. In addition, you can continue to develop your application with the open-source tools and platform of your choice to deliver your solutions without having to learn new skills.
 
@@ -29,7 +29,7 @@ Azure Blockchain Service offers two service tiers: *Basic* and *Standard*. Each
 
 ![Pricing tiers](./media/overview/pricing-tiers.png)
 
-In addition to offering two validator nodes, the *Standard* tier provides 2 *vCores* for each transaction and validator node whereas the Basic tier offers a 1 vCore configuration.  By offering 2 vCores for transaction and validator nodes, 1 vCore can be dedicated to the Quorum ledger while the remaining 1 vCore can be used for other infrastructure-related services, ensuring optimal performance for production blockchain workloads. For more information on pricing details, see [Azure Blockchain Service pricing](https://azure.microsoft.com/pricing/details/blockchain-service).
+In addition to offering two validator nodes, the *Standard* tier provides two *vCores* for each transaction and validator node whereas the *Basic* tier offers a 1 vCore configuration.  By offering 2 vCores for transaction and validator nodes, 1 vCore can be dedicated to the Quorum ledger while the remaining 1 vCore can be used for other infrastructure-related services, ensuring optimal performance for production blockchain workloads. For more information on pricing details, see [Azure Blockchain Service pricing](https://azure.microsoft.com/pricing/details/blockchain-service).
 
 ### Security and maintenance
 
