Merge pull request #33362 from Minewiskan/aas0214

rjagiewich · web-flow · commit 49c92be1839f · 2018-02-14T09:51:03.000-08:00
Aas0214
diff --git a/articles/analysis-services/analysis-services-async-refresh.md b/articles/analysis-services/analysis-services-async-refresh.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 12/18/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-backup.md b/articles/analysis-services/analysis-services-backup.md
@@ -13,7 +13,7 @@ ms.workload: data-management
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-bcdr.md b/articles/analysis-services/analysis-services-bcdr.md
@@ -13,7 +13,7 @@ ms.workload: data-management
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
@@ -27,13 +27,14 @@ While rare, an Azure data center can have an outage. When an outage occurs, it c
 
 * Deploy models to redundant servers in other regions. This method requires processing data on both your primary server and redundant servers in-parallel, assuring all servers are in-sync.
 
-* Back up databases from your primary server and restore on redundant servers. For example, you can automate nightly backups to Azure storage, and restore to other redundant servers in other regions. 
+* [Backup](analysis-services-backup.md) databases from your primary server and restore on redundant servers. For example, you can automate nightly backups to Azure storage, and restore to other redundant servers in other regions. 
 
 In either case, if your primary server experiences an outage, you must change the connection strings in reporting clients to connect to the server in a different regional datacenter. This change should be considered a last resort and only if a catastrophic regional data center outage occurs. It's more likely a data center outage hosting your primary server would come back online before you could update connections on all clients. 
 
-
+To avoid having to change connection strings on reporting clients, you can create a server [alias](analysis-services-server-alias.md) for your primary server. If the primary server goes down, you can change the alias to point to a redundant server in another region. You can automate alias to server name by coding an endpoint health check on the primary server. If the health check fails, the same endpoint can direct to a redundant server in another region. 
 
 ## Related information
 [Backup and restore](analysis-services-backup.md)   
-[Manage Azure Analysis Services](analysis-services-manage.md) 
+[Manage Azure Analysis Services](analysis-services-manage.md)   
+[Alias server names](analysis-services-server-alias.md) 
 
diff --git a/articles/analysis-services/analysis-services-compat-level.md b/articles/analysis-services/analysis-services-compat-level.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-connect-excel.md b/articles/analysis-services/analysis-services-connect-excel.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-connect.md b/articles/analysis-services/analysis-services-connect.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-create-model-portal.md b/articles/analysis-services/analysis-services-create-model-portal.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-create-powershell.md b/articles/analysis-services/analysis-services-create-powershell.md
@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: hero-article
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 ms.custom: mvc
 
diff --git a/articles/analysis-services/analysis-services-create-server.md b/articles/analysis-services/analysis-services-create-server.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-data-providers.md b/articles/analysis-services/analysis-services-data-providers.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 12/14/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-database-users.md b/articles/analysis-services/analysis-services-database-users.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-datasource.md b/articles/analysis-services/analysis-services-datasource.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-deploy.md b/articles/analysis-services/analysis-services-deploy.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: get-started-article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-gateway-install.md b/articles/analysis-services/analysis-services-gateway-install.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 10/30/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-logging.md b/articles/analysis-services/analysis-services-logging.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic:
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 12/29/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
@@ -80,12 +80,12 @@ The Metrics category logs the same [Server metrics](analysis-services-monitor.md
 
     ![Turn on diagnostic logging for Azure Cosmos DB in the Azure portal](./media/analysis-services-logging/aas-logging-turn-on-diagnostics.png)
 
-2. In **Diagnostic settings**, do the following: 
+2. In **Diagnostic settings**, specify the following options: 
 
     * **Name**. Enter a name for the logs to create.
 
-    * **Archive to a storage account**. To use this option, you need an existing storage account to connect to. See [Create a storage account](../storage/common/storage-create-storage-account.md). Follow the instructions to create a Resource Manager, general-purpose account. Then return to this page in the portal to select your storage account. It may take a few minutes for newly created storage accounts to appear in the drop-down menu.
-    * **Stream to an event hub**. To use this option, you need an existing Event Hub namespace and event hub to connect to. To create an Event Hubs namespace, see [Create an Event Hubs namespace and an event hub using the Azure portal](../event-hubs/event-hubs-create.md). Then return to this page in the portal to select the Event Hub namespace and policy name.
+    * **Archive to a storage account**. To use this option, you need an existing storage account to connect to. See [Create a storage account](../storage/common/storage-create-storage-account.md). Follow the instructions to create a Resource Manager, general-purpose account, then select your storage account by returning to this page in the portal. It may take a few minutes for newly created storage accounts to appear in the drop-down menu.
+    * **Stream to an event hub**. To use this option, you need an existing Event Hub namespace and event hub to connect to. To learn more, see [Create an Event Hubs namespace and an event hub using the Azure portal](../event-hubs/event-hubs-create.md). Then return to this page in the portal to select the Event Hub namespace and policy name.
     * **Send to Log Analytics**. To use this option, either use an existing workspace or create a new Log Analytics workspace by following the steps to [create a new workspace](../log-analytics/log-analytics-quick-collect-azurevm.md#create-a-workspace) in the portal. For more information on viewing your logs in Log Analytics, see [View logs in Log Analytics](#view-in-loganalytics).
 
     * **Engine**. Select this option to log xEvents. If you're archiving to a storage account, you can select the retention period for the diagnostic logs. Logs are autodeleted after the retention period expires.
@@ -168,7 +168,7 @@ In **Type**, click **AzureDiagnostics**, and then click **Apply**. AzureDiagnost
 
 Click **EventClass\_s** or one of the event names and Log Analytics continues constructing a query. Be sure to save your queries to reuse later.
 
-Be sure to checkout Operations Management Suite, which provides a website with enhanced query, dashboarding, and alerting capabilities on Log Analytics data.
+Be sure to see Operations Management Suite, which provides a website with enhanced query, dashboarding, and alerting capabilities on Log Analytics data.
 
 ### Queries
 
diff --git a/articles/analysis-services/analysis-services-manage-users.md b/articles/analysis-services/analysis-services-manage-users.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 10/09/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-manage.md b/articles/analysis-services/analysis-services-manage.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-monitor.md b/articles/analysis-services/analysis-services-monitor.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 09/14/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-odc.md b/articles/analysis-services/analysis-services-odc.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-overview.md b/articles/analysis-services/analysis-services-overview.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: get-started-article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 01/04/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-powershell.md b/articles/analysis-services/analysis-services-powershell.md
@@ -13,7 +13,7 @@ ms.workload: data-management
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-samples.md b/articles/analysis-services/analysis-services-samples.md
@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 10/10/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-scale-out.md b/articles/analysis-services/analysis-services-scale-out.md
@@ -13,7 +13,7 @@ ms.workload: data-management
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 11/06/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/analysis-services-server-admins.md b/articles/analysis-services/analysis-services-server-admins.md
@@ -14,17 +14,17 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: NA
 ms.workload: na
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
 # Manage server administrators
-Server administrators must be a valid user or group in the Azure Active Directory (Azure AD) for the tenant in which the server resides. You can use **Analysis Services Admins** in the control blade for your server in Azure portal, or Server Properties in SSMS to manage server administrators. 
+Server administrators must be a valid user or group in the Azure Active Directory (Azure AD) for the tenant in which the server resides. You can use **Analysis Services Admins** for your server in Azure portal, or Server Properties in SSMS to manage server administrators. 
 
 ## To add server administrators by using Azure portal
-1. In the control blade for your server, click **Analysis Services Admins**.
-2. In the **\<servername> - Analysis Services Admins** blade, click **Add**.
-3. In the **Add Server Administrators** blade, select user accounts from your Azure AD or invite external users by email address.
+1. In the the portal, for your server, click **Analysis Services Admins**.
+2. In **\<servername> - Analysis Services Admins**, click **Add**.
+3. In **Add Server Administrators**, select user accounts from your Azure AD or invite external users by email address.
 
     ![Server Admins in Azure portal](./media/analysis-services-server-admins/aas-manage-users-admins.png)
 
diff --git a/articles/analysis-services/analysis-services-server-alias.md b/articles/analysis-services/analysis-services-server-alias.md
@@ -13,7 +13,7 @@ ms.workload: data-management
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 11/01/2017
+ms.date: 02/14/2018
 ms.author: owend
 
 ---
diff --git a/articles/analysis-services/index.md b/articles/analysis-services/index.md
@@ -10,7 +10,7 @@ ms.service: analysis-services
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: landing-page
-ms.date: 01/23/2017
+ms.date: 02/14/2018
 ms.author: carolz
 ---
 # Analysis Services Documentation
diff --git a/articles/analysis-services/tutorials/aas-adventure-works-tutorial.md b/articles/analysis-services/tutorials/aas-adventure-works-tutorial.md
@@ -21,7 +21,7 @@ ms.author: owend
 
 This tutorial provides lessons on how to create and deploy a tabular model at the 1400 compatibility level by using Visual Studio with [SQL Server Data Tools (SSDT)](https://docs.microsoft.com/sql/ssdt/download-sql-server-data-tools-ssdt).  
 
-If you're new to Analysis Services and tabular modeling, completing this tutorial is the quickest way to learn how to create and deploy a basic tabular model by usign Visual Studio. Once you have the prerequisites in-place, it should take between two to three hours to complete.  
+If you're new to Analysis Services and tabular modeling, completing this tutorial is the quickest way to learn how to create and deploy a basic tabular model by using Visual Studio. Once you have the prerequisites in-place, it should take between two to three hours to complete.  
   
 ## What you learn   
   
@@ -39,7 +39,7 @@ If you're new to Analysis Services and tabular modeling, completing this tutoria
   
 -   How to secure model objects and data by creating roles with user members.  
   
--   How to deploy a tabular model to an **Azure Analysis Services** server or an on-premises SQL Server 2017 Analysis Services server.  
+-   How to deploy a tabular model to an **Azure Analysis Services** server or **SQL Server 2017 Analysis Services** server by using SSDT.  
   
 ## Prerequisites  
 To complete this tutorial, you need:  
diff --git a/articles/analysis-services/tutorials/aas-lesson-13-deploy.md b/articles/analysis-services/tutorials/aas-lesson-13-deploy.md
@@ -24,7 +24,7 @@ In this lesson, you configure deployment properties; specifying an Azure Analysi
 Estimated time to complete this lesson: **5 minutes**  
   
 ## Prerequisites  
-This topic is part of a tabular modeling tutorial, which should be completed in order. Before performing the tasks in this lesson, you should have completed the previous lesson: [Lesson 12: Analyze in Excel](../tutorials/aas-lesson-12-analyze-in-excel.md).  
+This article is part of a tabular modeling tutorial, which should be completed in order. Before performing the tasks in this lesson, you should have completed the previous lesson: [Lesson 12: Analyze in Excel](../tutorials/aas-lesson-12-analyze-in-excel.md).  
 
 > [!IMPORTANT]  
 > You must have [Administrator permissions](../analysis-services-server-admins.md) on the remote Analysis Services server in-order to deploy to it.  
@@ -63,6 +63,9 @@ This topic is part of a tabular modeling tutorial, which should be completed in
   
 3. When deployment successfully completes, go ahead and click **Close**.  
   
+
+This lesson describes the most common and easiest method to deploy a tabular model from SSDT. Advanced deployment options such as the Deployment Wizard or automating with XMLA and AMO provide greater flexibility, consistency, and scheduled deployments. To learn more, see [Tabular model solution deployment](https://docs.microsoft.com/sql/analysis-services/tabular-models/tabular-model-solution-deployment-ssas-tabular).
+
 ## Conclusion  
 Congratulations! You're finished authoring and deploying your first Analysis Services Tabular model. This tutorial has helped guide you through completing the most common tasks in creating a tabular model. Now that your Adventure Works Internet Sales model is deployed, you can use SQL Server Management Studio to manage the model; create process scripts and a backup plan. Users can also now connect to the model using a reporting client application such as Microsoft Excel or Power BI.  
 
