Bringing even with master.

Author: v-alje

.openpublishing.publish.config.json

@@ -259,6 +259,18 @@
       "url": "https://github.com/Azure-Samples/cognitive-services-java-sdk-samples",
       "branch": "master",
       "branch_mapping": {}
+    },
+    {
+      "path_to_root": "aml-sdk-samples",
+      "url": "https://github.com/Azure/MachineLearningNotebooks",
+      "branch": "sdk-codetest",
+      "branch_mapping": {}
+    },
+    {
+      "path_to_root": "cognitive-services-vision-csharp-sdk-quickstarts",
+      "url": "https://github.com/Azure-Samples/cognitive-services-vision-csharp-sdk-quickstarts",
+      "branch": "master",
+      "branch_mapping": {}
     }
   ],
   "branch_target_mapping": {

articles/active-directory-b2c/oauth2-technical-profile.md

@@ -42,7 +42,7 @@ The **InputClaims** and **InputClaimsTransformations** elements are not required
 
 ## Output claims
 
-The **OutputClaims** element contains a list of claims returned by the OAuth2 identity provider. You may need to map the name of the claim defined in your policy to the name defined in the identity provider. You can also include claims that aren't returned by the identity provider as long as the you set the `DefaultValue` attribute.
+The **OutputClaims** element contains a list of claims returned by the OAuth2 identity provider. You may need to map the name of the claim defined in your policy to the name defined in the identity provider. You can also include claims that aren't returned by the identity provider as long as you set the `DefaultValue` attribute.
 
 The **OutputClaimsTransformations** element may contain a collection of **OutputClaimsTransformation** elements that are used to modify the output claims or generate new ones.
 

articles/active-directory-b2c/technical-profiles-overview.md

@@ -34,8 +34,7 @@ A technical profile enables these types of scenarios:
 - [SAML2](saml-technical-profile.md) - Federation with any SAML protocol identity provider.
 - [Self-Asserted](self-asserted-technical-profile.md) - Interact with the user. For example, collect the user's credential to sign in, render the sign-up page, or password reset.
 - **WsFed** - Federation with any WsFed protocol identity provider. 
-- **Session management** - Handle different types of sessions. 
-- **User journey context provider**
+- [Session management](active-directory-b2c-reference-sso-custom.md) - Handle different types of sessions. 
 - **Application insights**
 
 ## Technical profile flow

articles/active-directory/develop/howto-reactivate-disabled-acs-namespaces.md

@@ -22,16 +22,16 @@ ms.custom: aaddev
 
 On November 2017, we announced that Microsoft Azure Access Control Service (ACS), a service of Azure Active Directory (Azure AD), is being retired on November 7, 2018.
 
-Since then, we've sent multiple emails to the ACS subscriptions’ admin email about the ACS retirement 12 months, 9 months, 6 months, 3 months, 1 month, 2 weeks, 1 week, and 1 day before the retirement date of November 7, 2018.
+Since then, we've sent emails to the ACS subscriptions’ admin email about the ACS retirement 12 months, 9 months, 6 months, 3 months, 1 month, 2 weeks, 1 week, and 1 day before the retirement date of November 7, 2018.
 
-On October 3, 2018, we announced (through email and [a blog post](https://azure.microsoft.com/blog/one-month-retirement-notice-access-control-service/)) an extension offer to customers who can't finish their migration before November 7, 2018. The announcement also contained instructions for requesting the extension.
+On October 3, 2018, we announced (through email and [a blog post](https://azure.microsoft.com/blog/one-month-retirement-notice-access-control-service/)) an extension offer to customers who can't finish their migration before November 7, 2018. The announcement also had instructions for requesting the extension.
 
 ## Why your namespace is disabled
 
-If you haven't opted in for the extension, we will start to disable ACS namespaces starting November 7, 2018. If you missed the communications and would still like to opt in for the extension to February 4, 2019, follow the instructions in the following sections.
+If you haven't opted in for the extension, we'll start to disable ACS namespaces starting November 7, 2018. If you missed the communications and would still like to opt in for the extension to February 4, 2019, follow the instructions in the following sections.
 
 > [!NOTE]
-> You must be an administrator of the subscription to run the PowerShell commands and request an extension. The permissions to log into the ACS namespace's management portal and PowerShell are the same. Service administrators and co-administrators can log in, but account administrators cannot log in.
+> You must be a service administrator or co-administrator of the subscription to run the PowerShell commands and request an extension.
 
 ## Find and enable your ACS namespaces
 
@@ -58,6 +58,9 @@ You can use ACS PowerShell to list all your ACS namespaces and reactivate ones t
         ```
     
         where `[Command-Name]` is the name of the ACS command.
+1. Connect to ACS using the **Connect-AcsAccount** cmdlet. 
+
+    You may need to change your execution policy by running **Set-ExecutionPolicy** before you can run the command.
 1. List your available Azure subscriptions using the **Get-AcsSubscription** cmdlet.
 1. List your ACS namespaces using the **Get-AcsNamespace** cmdlet.
 1. Confirm that the namespaces are disabled by confirming that `State` is `Disabled`.

articles/active-directory/manage-apps/configure-password-single-sign-on-non-gallery-applications.md

@@ -2,18 +2,13 @@
 title: How to configure password single sign-on for a non-gallery applicationn | Microsoft Docs
 description: How to configure an custom non-gallery application for secure password-based single sign-on when it is not listed in the Azure AD Application Gallery
 services: active-directory
-documentationcenter: ''
 author: barbkess
 manager: mtillman
-
-ms.assetid: 
 ms.service: active-directory
 ms.component: app-mgmt
 ms.workload: identity
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: conceptual
-ms.date: 07/11/2017
+ms.date: 11/12/2018
 ms.author: barbkess
 
 ---
@@ -112,7 +107,6 @@ To configure single sign-on for an application, follow these steps:
 
 11. Additionally, you can also provide credentials on behalf of the user by selecting the rows of the users and clicking on **Update Credentials** and entering the username and password on behalf of the users. Otherwise, users be prompted to enter the credentials themselves upon launch.
 
-12. **Optional:** For certain social media applications like Twitter and Facebook, there is also the option to enable automatic rollover of the password for the application at a selected frequency. To enable this select **I want Azure AD to automatically manage this user or group's password** while entering credentials on behalf of a user or group. Then select the **Rollover frequency (in weeks)**.
 
 ## Assign a user to an application directly
 

articles/active-directory/manage-apps/hide-application-from-user-portal.md

@@ -2,60 +2,53 @@
 title: Hide an application from user's experience in Azure Active Directory | Microsoft Docs
 description: How to hide an application from user's experience in Azure Active Directory access panels or Office 365 launchers.
 services: active-directory
-documentationcenter: ''
 author: barbkess
 manager: mtillman
-editor: ''
 ms.service: active-directory
 ms.component: app-mgmt
 ms.workload: identity
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: conceptual
-ms.date: 01/04/2018
+ms.date: 11/12/2018
 ms.author: barbkess
-ms.reviewer: asteen
-ms.custom: it-pro
+ms.reviewer: kasimpso
+
 ---
 
-# Hide an application from user's experience in Azure Active Directory
+# Hide applications from end-users in Azure Active Directory
+
+Instructions for how to hide applications from end-users' MyApps panel or Office 365 launcher. When an application is hidden, users still have permissions to the application. 
 
-If you have an application that you do not want to show on users’ access panels or Office 365 launchers, there are options to hide this app tile.  The following two options are available for hiding applications from user's app launchers.
+## Prerequisites
 
-- Hide a third-party application from users access panels and Office 365 app launchers
-- Hide all Office 365 applications from users access panels
+Application administrator privileges are required to hide an application from the MyApps panel and Office 365 launcher.
 
-By hiding the app users still have permissions to the app but will not see them appear on their app launchers. You must have the appropriate permissions to manage the enterprise app, and you must be a global admin for the directory.
+Global administrator privileges are required to hide all Office 365 applications.
 
 
-## Hiding an application from user's end user experiences
-You can use the steps below, depending on your situation, to hide applications from the access panel.
+## Hide an application from the end user
+Use the following steps to hide an application from MyApps panel and Office 365 application launcher.
 
-### How do I hide a third-party app from user’s access panel and O365 app launchers?
-Use the following steps to hide an application from a user's access panel and Office 365 app launchers.
+1.	Sign in to the [Azure portal](https://portal.azure.com) as the global administrator for your directory.
+2.	Select **Azure Active Directory**.
+3.	Select **Enterprise applications**. The **Enterprise applications - All applications** blade opens.
+4.	Under **Application Type**, select **Enterprise Applications**, if it isn't already selected.
+5.	Search for the application you want to hide, and click the application.  The application's overview opens.
+6.	Click **Properties**. 
+7.	For the **Visible to users?** question, click **No**.
+8.	Click **Save**.
 
-1.	Sign in to the [Azure portal](https://portal.azure.com) with an account that's a global admin for the directory.
-2.	Select **All services**, enter **Azure Active Directory** in the text box, and then select **Enter**.
-3.	On the **Azure Active Directory - *directoryname*** screen (that is, the Azure AD screen for the directory you are managing), select **Enterprise applications**.
-![Enterprise apps](./media/hide-application-from-user-portal/app1.png)
-4.	On the **Enterprise applications** screen, select **All applications**. You see a list of the apps you can manage.
-5.	On the **Enterprise applications - All applications** screen, select an app.</br>
-![Enterprise apps](./media/hide-application-from-user-portal/app2.png)
-6.	On the ***appname*** screen (that is, the screen with the name of the selected app in the title), select Properties.
-7.	On the ***appname* - Properties** screen, select **Yes** for **Visible to users?**.
-![Enterprise apps](./media/hide-application-from-user-portal/app3.png)
-8.	Select the **Save** command.
 
-### How do I hide Office 365 applications from user's access panel?
+## Hide Office 365 applications from the MyApps panel
 
-Use the following steps to hide all Office 365 applications from the access panel. These apps will still be visible in the Office 365 portal.
+Use the following steps to hide all Office 365 applications from the MyApps panel. The applications are still visible in the Office 365 portal.
 
-1.	Sign in to the [Azure portal](https://portal.azure.com) with an account that's a global admin for the directory.
-2.	Select **All services**, enter **Azure Active Directory** in the text box, and then select **Enter**.
-3.	On the **Azure Active Directory - *directoryname*** screen (that is, the Azure AD screen for the directory you are managing), select **User settings**.
-4.	On the **User settings** screen, under **Enterprise applications** select **Yes** for **Users can only see Office 365 apps in the Office 365 portal**.
+1.	Sign in to the [Azure portal](https://portal.azure.com) as a global administrator for your directory.
+2.	Select **Azure Active Directory**.
+3.	Select **User settings**.
+4.	Under **Enterprise applications**, click **Manage how end users launch and view their applications.**
+5.	For **Users can only see Office 365 apps in the Office 365 portal**, click **Yes**.
+6.	Click **Save**.
 
-![Enterprise apps](./media/hide-application-from-user-portal/apps4.png)
 
 ## Next steps
 * [See all my groups](../fundamentals/active-directory-groups-view-azure-portal.md)