Merge pull request MicrosoftDocs#45 from tysonn/master

daily update from master

articles/active-directory/active-directory-identityprotection-risk-events-types.md

@@ -14,7 +14,7 @@
 	ms.tgt_pltfrm="na"
 	ms.devlang="na"
 	ms.topic="article"
-	ms.date="10/20/2016"
+	ms.date="10/27/2016"
 	ms.author="markvi"/>
 
 #Types of risk events detected by Azure Active Directory Identity Protection 
@@ -72,7 +72,27 @@ This risk event type is a real-time sign-in evaluation mechanism that considers
 Unfamiliar locations can provide a strong indication that an attacker is able attempting to use a stolen identity. False-positives may occur when a user is traveling, trying out a new device or uses a new VPN. As a result of these false positives, the risk level for this event type is “**Medium**”.
 
 
+## Azure AD Anomalous Activity reports
 
+Some of these risk events have been available through the Azure AD Anomalous Activity reports in the Azure portal. 
+The table below lists the various risk event types and the corresponding **Azure AD Anomalous Activity** report. Microsoft is continuing to invest in this space, and plans to continuously improve the detection accuracy of existing risk events and add new risk event types on an ongoing basis. 
+
+
+
+| Identity Protection Risk Event Type | Corresponding Azure AD Anomalous Activity Report |
+| :-- | :-- |
+| Leaked credentials	| Users with leaked credentials |
+| Impossible travel to atypical locations |	Irregular sign-in activity |
+| Sign-ins from infected devices	| Sign-ins from possibly infected devices |
+| Sign-ins from anonymous IP addresses	| Sign-ins from unknown sources |
+| Sign-ins from IP addresses with suspicious activity |	Sign-ins from IP addresses with suspicious activity |
+| Signs in from unfamiliar locations	| - |
+| Lockout events	| - |
+
+The following Azure AD Anomalous Activity reports are not included as risk events in Azure AD Identity Protection, and will therefore not be available through Identity Protection. These reports are still available in the Azure portal however they will be deprecated at some time in the future as they are being superseded by risk events in Identity Protection.
+
+- Sign-ins after multiple failures
+- Sign-ins from multiple geographies
 
 
 ## See also

articles/active-directory/active-directory-identityprotection.md

@@ -72,25 +72,6 @@ But Azure Active Directory Identity Protection is more than a monitoring and rep
 
 Risk events are events that were flagged as suspicious by Identity Protection, and indicate that an identity may have been compromised. For a complete list of risk events, see [Types of risk events detected by Azure Active Directory Identity Protection](active-directory-identityprotection-risk-events-types.md). 
 
-Some of these risk events have been available through the Azure AD Anomalous Activity reports in the Azure portal. 
-The table below lists the various risk event types and the corresponding **Azure AD Anomalous Activity** report. Microsoft is continuing to invest in this space, and plans to continuously improve the detection accuracy of existing risk events and add new risk event types on an ongoing basis. 
-
-
-
-| Identity Protection Risk Event Type | Corresponding Azure AD Anomalous Activity Report |
-| :-- | :-- |
-| Leaked credentials	| Users with leaked credentials |
-| Impossible travel to atypical locations |	Irregular sign-in activity |
-| Sign-ins from infected devices	| Sign-ins from possibly infected devices |
-| Sign-ins from anonymous IP addresses	| Sign-ins from unknown sources |
-| Sign-ins from IP addresses with suspicious activity |	Sign-ins from IP addresses with suspicious activity |
-| Signs in from unfamiliar locations	| - |
-| Lockout events	| - |
-
-The following Azure AD Anomalous Activity reports are not included as risk events in Azure AD Identity Protection, and will therefore not be available through Identity Protection. These reports are still available in the Azure portal however they will be deprecated at some time in the future as they are being superseded by risk events in Identity Protection.
-
-- Sign-ins after multiple failures
-- Sign-ins from multiple geographies
 
 ### Risk level
 

articles/active-directory/active-directory-saas-tutorial-list.md

@@ -13,7 +13,7 @@
     ms.topic="article"
     ms.tgt_pltfrm="na"
     ms.workload="identity"
-    ms.date="10/25/2016"
+    ms.date="10/26/2016"
     ms.author="markvi"/>
 
 #List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory
@@ -75,6 +75,7 @@ For the comprehensive list of SaaS apps that have been pre-integrated into Azure
 | ![logo](./media/active-directory-saas-tutorial-list/SaaSApp_Central_Desktop.png)| [Central Desktop](https://go.microsoft.com/fwLink/?LinkID=403249&clcid=0x409)|
 | ![logo](./media/active-directory-saas-tutorial-list/SaaSApp_Ceridian.png)| [Ceridian Dayforce HCM](https://go.microsoft.com/fwLink/?LinkID=733445&clcid=0x409)|
 | ![logo](./media/active-directory-saas-tutorial-list/SaaSApp_Certify.png)| [Certify](http://go.microsoft.com/fwlink/?LinkID=708681&clcid=0x409)|
+| ![logo](./media/active-directory-saas-tutorial-list/SaaSApp_CezanneHR_Software.png)| [Cezanne HR Software](https://go.microsoft.com/fwLink/?LinkID=823734&clcid=0x409)|
 | ![logo](./media/active-directory-saas-tutorial-list/SaaSApp_Cherwell.png)| [Cherwell](https://go.microsoft.com/fwLink/?LinkID=530225&clcid=0x409)|
 | ![logo](./media/active-directory-saas-tutorial-list/SaaSApp_Chromeriver.png)| [Chromeriver](https://go.microsoft.com/fwLink/?LinkID=530233&clcid=0x409)|
 | ![logo](./media/active-directory-saas-tutorial-list/SaaSApp_Cimpl.png)| [Cimpl](https://go.microsoft.com/fwLink/?LinkID=708685&clcid=0x409)|
@@ -292,6 +293,7 @@ For the comprehensive list of SaaS apps that have been pre-integrated into Azure
 
 
 
+
 ##Related Articles
 
 - [Article Index for Application Management in Azure Active Directory](active-directory-apps-index.md)

articles/active-directory/active-directory-users-create-external-azure-portal.md

@@ -41,8 +41,8 @@ This article explains how to add users either from other directories in Azure Ac
 5. Copy or otherwise note the generated user password so that you can provide it to the user after this process is complete.
 
 6. Optionally, select **Profile** to add the users first and last name, a job title, and a department name.
-
-		![Opening the user profile](./media/active-directory-users-create-external-azure-portal/create-users-user-profile.png)
+	
+    ![Opening the user profile](./media/active-directory-users-create-external-azure-portal/create-users-user-profile.png)
 
 	- Select **Groups** to add the user to one or more groups.
 

articles/analysis-services/analysis-services-manage.md

@@ -45,6 +45,8 @@ Connecting to your server in Azure is just like connecting to a server instance
 
     **Active Directory Password Authentication** to use an organizational account. For example, when connecting from a non-domain joined computer.
 
+    Note: If you don't see Active Directory Authentication, you may need to [enable Azure Active Directory authentication](#enable-azure-active-directory-authentication) in SSMS.
+
     ![Connect in SSMS](./media/analysis-services-manage/aas-manage-connect-ssms.png)
 
 Since managing your server in Azure by using SSMS is much the same as managing an on-premises server, we're not going to go into details here. All the help you need can be found in [Analysis Services Instance Management](https://msdn.microsoft.com/library/hh230806.aspx) on MSDN.
@@ -95,6 +97,20 @@ You can add users by using [role assignments in Azure Active Directory](../activ
 }
 ```
 
+## Enable Azure Active Directory authentication
+To enable the Azure Active Directory authentication feature for SSMS in the registry, create a text file named EnableAAD.reg, then copy and paste the following:
+
+
+```
+Windows Registry Editor Version 5.00
+[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\Microsoft Analysis Services\Settings]
+"AS AAD Enabled"="True"
+```
+
+Save and then run the file.
+
+
+
 ## Next steps
 If you haven't already deployed a tabular model to your new server, now is a good time. To learn more, see [Deploy to Azure Analysis Services](analysis-services-deploy.md).
 

articles/api-management/api-management-log-to-eventhub-sample.md

@@ -4,7 +4,7 @@
     services="api-management"
     documentationCenter=""
     authors="darrelmiller"
-    manager=""
+    manager="erikre"
     editor=""/>
 
 <tags

articles/api-management/api-management-sample-cache-by-key.md

@@ -4,7 +4,7 @@
 	services="api-management"
 	documentationCenter=""
 	authors="darrelmiller"
-	manager=""
+	manager="erikre"
 	editor=""/>
 
 <tags

articles/api-management/api-management-sample-flexible-throttling.md

@@ -4,7 +4,7 @@
 	services="api-management"
 	documentationCenter=""
 	authors="darrelmiller"
-	manager=""
+	manager="erikre"
 	editor=""/>
 
 <tags

articles/api-management/api-management-sample-send-request.md

@@ -4,7 +4,7 @@
 	services="api-management"
 	documentationCenter=""
 	authors="darrelmiller"
-	manager=""
+	manager="erikre"
 	editor=""/>
 
 <tags

articles/app-service-logic/app-service-logic-scenario-error-and-exception-handling.md

@@ -4,7 +4,7 @@
     keywords=""
     services="logic-apps"
     authors="hedidin"
-    manager=""
+    manager="anneta"
     editor=""
     documentationCenter=""/>
 

articles/app-service-mobile/app-service-mobile-android-get-started-offline-data.md

@@ -2,7 +2,7 @@
 	pageTitle="Enable offline sync for your Azure Mobile App (Android)"
 	description="Learn how to use App Service Mobile Apps to cache and sync offline data in your Android application"
 	documentationCenter="android"
-	authors="yuaxu"
+	authors="ysxu"
 	manager="erikre"
 	services="app-service\mobile"/>
 
@@ -21,17 +21,17 @@
 
 ## Overview
 
-This tutorial covers the offline sync feature of Azure Mobile Apps for Android. Offline sync allows end-users to interact with a mobile app—viewing, adding, or modifying data—even when there is no network connection. Changes are stored in a local database; once the device is back online, these changes are synced with the remote backend.
+This tutorial covers the offline sync feature of Azure Mobile Apps for Android. Offline sync allows end users to interact with a mobile app—viewing, adding, or modifying data—even when there is no network connection. Changes are stored in a local database. Once the device is back online, these changes are synced with the remote backend.
 
 If this is your first experience with Azure Mobile Apps, you should first complete the tutorial [Create an Android App]. If you do not use the downloaded quick start server project, you must add the data access extension packages to your project. For more information about server extension packages, see [Work with the .NET backend server SDK for Azure Mobile Apps](app-service-mobile-dotnet-backend-how-to-use-server-sdk.md).
 
 To learn more about the offline sync feature, see the topic [Offline Data Sync in Azure Mobile Apps].
 
 ## Update the app to support offline sync
 
-With offline sync you read to and write from a *sync table* (using the *IMobileServiceSyncTable* interface), which is part of a **SQLite** database on your device.
+With offline sync, you read to and write from a *sync table* (using the *IMobileServiceSyncTable* interface), which is part of a **SQLite** database on your device.
 
-To push and pull changes between the device and Azure Mobile Services, you use a *synchronization context* (*MobileServiceClient.SyncContext*), which you initialize with the local database that you use to store data locally.
+To push and pull changes between the device and Azure Mobile Services, you use a *synchronization context* (*MobileServiceClient.SyncContext*), which you initialize with the local database to store data locally.
 
 1. In `TodoActivity.java`, comment out the existing definition of `mToDoTable` and uncomment the sync table version:
 
@@ -79,11 +79,11 @@ To push and pull changes between the device and Azure Mobile Services, you use a
 
 ## Test the app
 
-In this section, you will test the behavior with WiFi on, and then turn off WiFi to create an offline scenario.
+In this section, you test the behavior with WiFi on, and then turn off WiFi to create an offline scenario.
 
 When you add data items, they are held in the local SQLite store, but not synced to the mobile service until you press the **Refresh** button. Other apps may have different requirements regarding when data needs to be synchronized, but for demo purposes this tutorial has the user explicitly request it.
 
-When you press that button, a new background task starts, and first pushes all the changes made to the local store, by using the synchronization context, and then pulls all changed data from Azure to the local table.
+When you press that button, a new background task starts. It first pushes all changes made to the local store using synchronization context, then pulls all changed data from Azure to the local table.
 
 ### Offline testing
 

articles/app-service-mobile/app-service-mobile-android-get-started-push.md

@@ -1,51 +1,53 @@
 <properties
-	pageTitle="Add Push Notifications to Android App with Azure  Mobile Apps"
+	pageTitle="Add Push Notifications to Android App with Azure Mobile Apps"
 	description="Learn how to use Azure Mobile Apps to send push notifications to your Android app."
 	services="app-service\mobile"
 	documentationCenter="android"
 	manager="erikre"
 	editor=""
-	authors="yuaxu"/>
+	authors="ysxu"/>
 
 <tags
 	ms.service="app-service-mobile"
 	ms.workload="mobile"
 	ms.tgt_pltfrm="mobile-android"
 	ms.devlang="java"
 	ms.topic="article"
-	ms.date="10/01/2016"
+	ms.date="10/12/2016"
 	ms.author="yuaxu"/>
 
 # Add Push Notifications to your Android App
 
 [AZURE.INCLUDE [app-service-mobile-selector-get-started-push](../../includes/app-service-mobile-selector-get-started-push.md)]
 
 ## Overview
-This tutorial shows you how to add push notifications to the [Android quick start] project so that every time a record is inserted, a push notification is sent. This tutorial is based on the [Android quick start] tutorial, which you must complete first. If you do not use the downloaded quick start server project, you must add the push notification extension package to your project. For more information about server extension packages, see [Work with the .NET backend server SDK for Azure Mobile Apps](app-service-mobile-dotnet-backend-how-to-use-server-sdk.md).
+In this tutorial, you add push notifications to the [Android quick start] project so that a push notification is sent to the device every time a record is inserted.
 
-## Prerequisites
+If you do not use the downloaded quick start server project, you need the push notification extension package. For more information, see [Work with the .NET backend server SDK for Azure Mobile Apps](app-service-mobile-dotnet-backend-how-to-use-server-sdk.md).
 
-The following items are needed to complete this tutorial:
+## Prerequisites
 
-* [Google account](http://go.microsoft.com/fwlink/p/?LinkId=268302) with a verified email address.
+You need the following:
 
 * An IDE depending on your project's backend:
 
 	* [Android Studio](https://developer.android.com/sdk/index.html) if this app has a Node.js backend.
 
 	* [Visual Studio Community 2013](https://go.microsoft.com/fwLink/p/?LinkID=391934) or later if this app has a .Net backend.
 
-* Complete the [quickstart tutorial](app-service-mobile-android-get-started.md).
+* Android 2.3 or higher, Google Repository revision 27 or higher, and Google Play Services 9.0.2 or higher for Firebase Cloud Messaging.
+
+* Complete the [Android quick start].
 
 ## Create a project that supports Firebase Cloud Messaging
 
 [AZURE.INCLUDE [notification-hubs-enable-firebase-cloud-messaging](../../includes/notification-hubs-enable-firebase-cloud-messaging.md)]
 
-## Create a Notification Hub
+## Configure a Notification Hub
 
-[AZURE.INCLUDE [app-service-mobile-create-notification-hub](../../includes/app-service-mobile-create-notification-hub.md)]
+[AZURE.INCLUDE [app-service-mobile-configure-notification-hub](../../includes/app-service-mobile-configure-notification-hub.md)]
 
-## Configure the Mobile App backend for sending push requests
+## Configure Azure to send push notifications
 
 [AZURE.INCLUDE [app-service-mobile-android-configure-push](../../includes/app-service-mobile-android-configure-push-for-firebase.md)]
 
@@ -55,7 +57,7 @@ The following items are needed to complete this tutorial:
 
 ## Add push notifications to your app
 
-In this section, you enable your Android app project to handle push notifications.
+In this section, you update your client Android app to handle push notifications.
 
 ### Verify Android SDK Version
 
@@ -79,8 +81,6 @@ You can test the app by directly attaching an Android phone with a USB cable, or
 
 ## More
 
-* Tags allow you to target segmented customers with pushes. [Work with the .NET backend server SDK for Azure Mobile Apps](app-service-mobile-dotnet-backend-how-to-use-server-sdk.md) shows you how to add tags to a device installation.
-
 <!-- URLs -->
 [Android quick start]: app-service-mobile-android-get-started.md
 

articles/app-service-mobile/app-service-mobile-android-get-started-users.md

@@ -3,7 +3,7 @@
 	description="Learn how to use Mobile Apps in Azure App Service to authenticate users of your Android app through a variety of identity providers, including Google, Facebook, Twitter, and Microsoft."
 	services="app-service\mobile"
 	documentationCenter="android"
-	authors="yuaxu"
+	authors="ysxu"
 	manager="erikre"
 	editor=""/>
 
@@ -32,11 +32,11 @@ In this tutorial, you add authentication to the todolist quickstart project on A
 
 [AZURE.INCLUDE [app-service-mobile-restrict-permissions-dotnet-backend](../../includes/app-service-mobile-restrict-permissions-dotnet-backend.md)]
 
-+ In Android Studio, open the project that you created when you completed the tutorial [Get started with Mobile Apps], then from the **Run** menu click **Run app** and verify that an unhandled exception with a status code of 401 (Unauthorized) is raised after the app starts.
++ In Android Studio, open the project the projected you completed with the tutorial [Get started with Mobile Apps]. From the **Run** menu click **Run app** and verify that an unhandled exception with a status code of 401 (Unauthorized) is raised after the app starts.
 
-	 This happens because the app attempts to access the backend as an unauthenticated user, but the _TodoItem_ table now requires authentication.
+	 This exception happens because the app attempts to access the backend as an unauthenticated user, but the _TodoItem_ table now requires authentication.
 
-Next, you will update the app to authenticate users before requesting resources from the Mobile App backend.
+Next, you update the app to authenticate users before requesting resources from the Mobile App backend.
 
 ## Add authentication to the app
 
@@ -51,10 +51,10 @@ Next, you will update the app to authenticate users before requesting resources
 Now that you completed this basic authentication tutorial, consider continuing on to one of the following tutorials:
 
 + [Add push notifications to your Android app](app-service-mobile-android-get-started-push.md)
-  Learn how to add push notifications support to your app and configure your Mobile App backend to use Azure Notification Hubs to send push notifications.
+  Learn how to configure your Mobile App backend to use Azure Notification Hubs to send push notifications.
 
 + [Enable offline sync for your Android app](app-service-mobile-android-get-started-offline-data.md)
-  Learn how to add offline support your app using an Mobile App backend. Offline sync allows end-users to interact with a mobile app—viewing, adding, or modifying data—even when there is no network connection.
+  Learn how to add offline support your app using a Mobile App backend. Offline sync allows end users to interact with a mobile app—viewing, adding, or modifying data—even when there is no network connection.
 
 
 

articles/app-service-mobile/app-service-mobile-android-get-started.md

@@ -3,7 +3,7 @@
     description="Follow this tutorial to get started with using Azure mobile app backends for Android development"
     services="app-service\mobile"
     documentationCenter="android"
-    authors="yuaxu"
+    authors="ysxu"
     manager="erikre"
     editor=""/>
 
@@ -46,9 +46,6 @@ To complete this tutorial, you need the following:
 
 [AZURE.INCLUDE [app-service-mobile-android-run-app](../../includes/app-service-mobile-android-run-app.md)]
 
-
-<!-- Images. -->
-
 <!-- URLs -->
 [Azure portal]: https://portal.azure.com/
 [Visual Studio Community 2013]: https://go.microsoft.com/fwLink/p/?LinkID=534203