MicrosoftDocs · v-anpasi · Jan 9, 2017 · Dec 5, 2016 · Dec 5, 2016 · Dec 15, 2016
diff --git a/articles/azure-government/documentation-government-overview-dod.md b/articles/azure-government/documentation-government-overview-dod.md
@@ -20,7 +20,7 @@ ms.author: ryansoc
 ---
 # Department of Defense (DoD) in Azure Government
 ## Overview
-Azure Government is used by Department of Defense (DoD) entities to deploy a broad range of workloads and solutions, including those workloads covered by<a href="http://iasecontent.disa.mil/cloud/SRG/index.html"> The DoD Cloud Computing Security Requirements Guide, Version 1, Release 2</a> at Impact Level 4 (L4).
+Azure Government is used by Department of Defense (DoD) entities to deploy a broad range of workloads and solutions, including those workloads covered by<a href="http://iasecontent.disa.mil/cloud/SRG/index.html"> The DoD Cloud Computing Security Requirements Guide, Version 1, Release 2</a> at Impact Level 4 (L4), and Impact Level 5 (L5).
 
 One of the key drivers for the DoD in moving to the cloud is to enable organizations to focus on their missions and minimize the distractions of building and managing in-house IT solutions.
 

diff --git a/articles/backup/backup-azure-vms-automation.md b/articles/backup/backup-azure-vms-automation.md
@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: storage-backup-recovery
-ms.date: 11/01/2016
+ms.date: 01/09/2017
 ms.author: markgal; trinadhk
 
 ---
@@ -196,6 +196,11 @@ PS C:\> $pol=Get-AzureRmRecoveryServicesBackupProtectionPolicy -Name "NewPolicy"
 PS C:\> Enable-AzureRmRecoveryServicesBackupProtection -Policy $pol -Name "V2VM" -ResourceGroupName "RGName1"
 ```
 
+> [!NOTE]
+> If you are on Azure Government cloud, then use the value ff281ffe-705c-4f53-9f37-a40e6f2c68f3 for the parameter **-ServicePrincipalName** in Set-AzureRmKeyVaultAccessPolicy cmdlet.
+> 
+> 
+
 For ASM based VMs
 
 ```
@@ -227,7 +232,8 @@ WorkloadName     Operation            Status               StartTime
 V2VM              Backup               InProgress            4/23/2016 5:00:30 PM                       cf4b3ef5-2fac-4c8e-a215-d2eba4124f27
 ```
 
-> [AZURE.NOTE: The timezone of the StartTime and EndTime fields in PowerShell is UTC. However, when the time is shown in the Azure portal, the time is adjusted to your local timezone.
+> [!NOTE]
+> The timezone of the StartTime and EndTime fields in PowerShell is UTC. However, when the time is shown in the Azure portal, the time is adjusted to your local timezone.
 > 
 > 
 

diff --git a/articles/batch/batch-cli-get-started.md b/articles/batch/batch-cli-get-started.md
@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: get-started-article
 ms.tgt_pltfrm: multiple
 ms.workload: big-compute
-ms.date: 09/30/2016
+ms.date: 01/05/2017
 ms.author: tamram
 
 ---

diff --git a/articles/batch/batch-job-prep-release.md b/articles/batch/batch-job-prep-release.md
@@ -13,7 +13,7 @@ ms.devlang: multiple
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: big-compute
-ms.date: 09/16/2016
+ms.date: 01/04/2017
 ms.author: tamram
 
 ---

diff --git a/articles/batch/batch-quota-limit.md b/articles/batch/batch-quota-limit.md
@@ -13,7 +13,7 @@ ms.workload: big-compute
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 09/10/2016
+ms.date: 01/05/2017
 ms.author: tamram
 
 ---

diff --git a/articles/batch/batch-task-dependencies.md b/articles/batch/batch-task-dependencies.md
@@ -13,7 +13,7 @@ ms.devlang: multiple
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: big-compute
-ms.date: 09/28/2016
+ms.date: 01/05/2017
 ms.author: tamram
 
 ---

diff --git a/articles/batch/batch-task-output.md b/articles/batch/batch-task-output.md
@@ -13,7 +13,7 @@ ms.devlang: multiple
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: big-compute
-ms.date: 09/07/2016
+ms.date: 01/05/2017
 ms.author: tamram
 
 ---

diff --git a/articles/batch/batch-visual-studio-templates.md b/articles/batch/batch-visual-studio-templates.md
@@ -13,7 +13,7 @@ ms.devlang: multiple
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: big-compute
-ms.date: 09/07/2016
+ms.date: 01/05/2017
 ms.author: tamram
 
 ---

diff --git a/articles/cache/cache-dotnet-how-to-use-in-role.md b/articles/cache/cache-dotnet-how-to-use-in-role.md
@@ -13,7 +13,7 @@ ms.workload: web
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: article
-ms.date: 09/15/2016
+ms.date: 01/06/2017
 ms.author: sdanie
 
 ---

diff --git a/articles/cache/cache-dotnet-how-to-use-service.md b/articles/cache/cache-dotnet-how-to-use-service.md
@@ -13,7 +13,7 @@ ms.workload: web
 ms.tgt_pltfrm: na
 ms.devlang: dotnet
 ms.topic: article
-ms.date: 09/15/2016
+ms.date: 01/06/2017
 ms.author: sdanie
 
 ---

diff --git a/articles/event-hubs/event-hubs-management-libraries.md b/articles/event-hubs/event-hubs-management-libraries.md
@@ -0,0 +1,79 @@
+---
+  title: Azure Event Hubs Management Libraries | Microsoft Docs
+  description: Manage Event Hubs namespaces and entities from .NET
+  services: event-hubs
+  cloud: na
+  documentationcenter: na
+  author: jtaubensee
+  manager: sethm
+
+  ms.assetid:
+  ms.service: event-hubs
+  ms.workload: na
+  ms.tgt_pltfrm: na
+  ms.devlang: dotnet
+  ms.topic: article
+  ms.date: 1/6/2016
+  ms.author: jotaub
+
+---
+
+# Event Hubs management libraries
+
+The Event Hubs management libraries provide functionality to dynamically provision Event Hubs namespaces and entities. This allows for complex deployments and messaging scenarios, allowing users to programmatically determine what entities to provision. These libraries are currently available for .NET.
+
+## Supported functionality
+
+* Namespace creation, update, deletion
+* Event Hub creation, update, deletion
+* Consumer Group creation, update, deletion
+
+## Prerequisites
+
+In order to get started using the Event Hubs management libraries, you must authenticate with Azure Active Directory (AAD). AAD requires that you authenticate as a Service Principal which provides access to your Azure resources. For information on creating a Service Principal follow one of these articles:  
+
+* [Use the Azure Portal to create Active Directory application and service principal that can access resources](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal)
+* [Use Azure PowerShell to create a service principal to access resources](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authenticate-service-principal)
+* [Use Azure CLI to create a service principal to access resources](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authenticate-service-principal-cli)
+
+The previous tutorials will provide you with an `AppId` (Client ID), `TenantId`, and `ClientSecret` (Authentication Key), all of which will be used to authenticate by the management libraries. You must have 'Owner' permissions for the resource group that you wish to run on.
+
+## Programming pattern
+
+The pattern to manipulate any Event Hubs resource is similar and follows a common protocol:
+
+1. Obtain a token from Azure Active Directory using the `Microsoft.IdentityModel.Clients.ActiveDirectory` library.
+    ```csharp
+    var context = new AuthenticationContext($"https://login.windows.net/{tenantId}");
+
+    var result = await context.AcquireTokenAsync(
+        "https://management.core.windows.net/",
+        new ClientCredential(clientId, clientSecret)
+    );
+    ```
+
+1. Create the `EventHubManagementClient` object.
+    ```csharp
+    var creds = new TokenCredentials(token);
+    var ehClient = new EventHubManagementClient(creds)
+    {
+        SubscriptionId = SettingsCache["SubscriptionId"]
+    };
+    ```
+
+1. Set the CreateOrUpdate parameters to your specified values.
+    ```csharp
+    var ehParams = new EventHubCreateOrUpdateParameters()
+    {
+        Location = SettingsCache["DataCenterLocation"]
+    };
+    ```
+
+1. Execute the call.
+    ```csharp
+    await ehClient.EventHubs.CreateOrUpdateAsync(resourceGroupName, namespaceName, EventHubName, ehParams);
+    ```
+
+## Next steps
+* [.NET Management sample](https://github.com/Azure-Samples/event-hubs-dotnet-management/)
+* [Microsoft.Azure.Management.ServiceBus Reference](/dotnet/api/Microsoft.Azure.Management.EventHub) 
diff --git a/articles/hdinsight/hdinsight-apache-spark-use-bi-tools.md b/articles/hdinsight/hdinsight-apache-spark-use-bi-tools.md
@@ -14,7 +14,7 @@ ms.workload: big-data
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 10/05/2016
+ms.date: 01/06/2017
 ms.author: nitinme
 
 ---
@@ -24,11 +24,6 @@ Learn how to use Apache Spark in Azure HDInsight to do the following:
 * Take raw sample data and save it as a Hive table
 * Use BI tools such as Power BI and Tableau to analyze and visualize the data.
 
-> [!NOTE]
-> This tutorial is applicable only for Spark 1.5.2 clusters created in Azure HDInsight.
->
->
-
 This tutorial is also available as a Jupyter notebook on a Spark (Linux) cluster that you create in HDInsight. The notebook experience lets you run the Python snippets from the notebook itself. To perform the tutorial from within a notebook, create a Spark cluster, launch a Jupyter notebook (`https://CLUSTERNAME.azurehdinsight.net/jupyter`), and then run the notebook **Use BI tools with Apache Spark on HDInsight.ipynb** under the **Python** folder.
 
 **Prerequisites:**
@@ -136,6 +131,12 @@ Once you have saved the data as a Hive table, you can use Power BI to connect to
    You can add as many visualizations as you want for the same dataset and pin them to the dashboard for a snapshot of your data. Also, Spark clusters on HDInsight are connected to Power BI with direct connect. This means that Power BI always has the most up-to-date from your cluster so you do not need to schedule refreshes for the dataset.
 
 ## <a name="tableau"></a>Use Tableau Desktop to analyze data in the Hive table
+
+> [!NOTE]
+> This section is applicable only for Spark 1.5.2 clusters created in Azure HDInsight.
+>
+>
+
 1. Launch Tableau Desktop. In the left pane, from the list of server to connect to, click **Spark SQL**. If Spark SQL is not listed by default in the left pane, you can find it by click **More Servers**.
 2. In the Spark SQL connection dialog box, provide the values as shown below, and then click **OK**.