Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into aas-datasource

Author: Owen Duncan

.openpublishing.redirection.json

@@ -11462,6 +11462,11 @@
       "redirect_url": "/azure/event-hubs/",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/event-hubs/event-hubs-create-kafka-enabled.md",
+      "redirect_url": "/azure/event-hubs/event-hubs-create",
+      "redirect_document_id": false
+    },    
     {
       "source_path": "articles/event-hubs/event-hubs-csharp-ephcs-getstarted.md",
       "redirect_url": "/azure/event-hubs/event-hubs-dotnet-standard-getstarted-send",

articles/active-directory-b2c/active-directory-b2c-get-started-custom.md

@@ -30,7 +30,7 @@ ms.subservice: B2C
 1. Sign in to the [Azure portal](https://portal.azure.com)
 1. Use the **Directory + subscription** filter in the top menu to select the directory that contains your Azure AD B2C tenant.
 1. In the left menu, select **Azure AD B2C**. Or, select **All services** and search for and select **Azure AD B2C**.
-1. On the Overview page, select **Identity Experience Framework**.
+1. On the Overview page, select **Identity Experience Framework** from the **Policies** pane.
 
 ### Create the signing key
 

articles/active-directory-b2c/active-directory-b2c-reference-spa.md

@@ -245,5 +245,5 @@ GET https://{tenant}.b2clogin.com/{tenant}.onmicrosoft.com/{policy}/oauth2/v2.0/
 This sample on GitHub is intended to help get you started with Azure AD B2C in a simple web application built on [hello.js][github-hello-js] and using pop-up-style authentication.
 
 <!-- Links - EXTERNAL -->
-[github-hello-js-example]: https://github.com/azure-ad-b2c/apps/tree/master/spa/javascript-hellojs-singlepageapp-popup
+[github-hello-js-example]: https://github.com/Azure-Samples/active-directory-b2c-javascript-hellojs-singlepageapp
 [github-hello-js]: https://github.com/MrSwitch/hello.js

articles/active-directory-domain-services/tutorial-configure-ldaps.md

@@ -206,7 +206,7 @@ Let's create a rule to allow inbound secure LDAP access over TCP port 636 from a
 
 1. In the Azure portal, select *Resource groups* on the left-hand side navigation.
 1. Choose you resource group, such as *myResourceGroup*, then select your network security group, such as *aaads-nsg*.
-1. The list of existing inbound and outbound security rules are displayed. On the left-hand side of the network security group windows, choose **Security > Inbound security rules**.
+1. The list of existing inbound and outbound security rules are displayed. On the left-hand side of the network security group windows, choose **Settings > Inbound security rules**.
 1. Select **Add**, then create a rule to allow *TCP* port *636*. For improved security, choose the source as *IP Addresses* and then specify your own valid IP address or range for your organization.
 
     | Setting                           | Value        |
@@ -241,7 +241,7 @@ The following example DNS entry, either with your external DNS provider or in th
 
 ## Test queries to the managed domain
 
-To connect and bind to your Azure AD DS managed domain and search over LDAP, you use the *LDP.exe* too. This tool is included in the Remote Server Administration Tools (RSAT) package. For more information, see [install Remote Server Administration Tools][rsat].
+To connect and bind to your Azure AD DS managed domain and search over LDAP, you use the *LDP.exe* tool. This tool is included in the Remote Server Administration Tools (RSAT) package. For more information, see [install Remote Server Administration Tools][rsat].
 
 1. Open *LDP.exe* and connect to the managed domain. Select **Connection**, then choose **Connect...**.
 1. Enter the secure LDAP DNS domain name of your managed domain created in the previous step, such as *ldaps.contoso.com*. To use secure LDAP, set **Port** to *636*, then check the box for **SSL**.

articles/active-directory/develop/authentication-flows-app-scenarios.md

@@ -258,14 +258,14 @@ Scenarios that involve acquiring tokens also map to OAuth 2.0 authentication flo
 
   <tr>
    <td><a href="scenario-daemon-overview.md"><img alt="Daemon app that calls web APIs" src="media/scenarios/daemon-app.svg"></a></td>
-   <td><a href=scenario-daemon-overview.md">A daemon app that calls web APIs</a></td>
+   <td><a href="scenario-daemon-overview.md">A daemon app that calls web APIs</a></td>
    <td><a href="v2-oauth2-client-creds-grant-flow.md">Client credentials</a></td>
    <td>App-only permissions with no user and used only in Azure AD organizations</td>
  </tr>
 
   <tr>
-   <td><a href=scenario-web-api-call-api-overview.md"><img alt="Web API that calls web APIs" src="media/scenarios/web-api.svg"></a></td>
-   <td><a href=scenario-web-api-call-api-overview.md">A web API that calls web APIs</a></td>
+   <td><a href="scenario-web-api-call-api-overview.md"><img alt="Web API that calls web APIs" src="media/scenarios/web-api.svg"></a></td>
+   <td><a href="scenario-web-api-call-api-overview.md">A web API that calls web APIs</a></td>
    <td><a href="v2-oauth2-on-behalf-of-flow.md">On Behalf Of</a></td>
    <td>Work or school accounts and personal accounts</td>
  </tr>

articles/active-directory/fundamentals/active-directory-accessmanagement-managing-group-owners.md

@@ -16,7 +16,7 @@ ms.collection: M365-identity-device-management
 ---
 
 # Add or remove group owners in Azure Active Directory
-Azure Active Directory (Azure AD) groups are owned and managed by group owners. Group owners can be users or service principals, and are able to manage the group including membership. Only existing group owners or group-managing administrators can assign group onwers. Group owners aren't required to be members of the group.
+Azure Active Directory (Azure AD) groups are owned and managed by group owners. Group owners can be users or service principals, and are able to manage the group including membership. Only existing group owners or group-managing administrators can assign group owners. Group owners aren't required to be members of the group.
 
 When a group has no owner, group-managing administrators are still able to manage the group.
 

articles/active-directory/fundamentals/whats-new.md

@@ -547,13 +547,13 @@ For more information about setting up Azure Monitor, see [Azure AD activity logs
 
 On September 25, 2019, we'll be turning off the old, non-enhanced security info experience for registering and managing user security info and only turning on the new, [enhanced version](https://techcommunity.microsoft.com/t5/Azure-Active-Directory-Identity/Cool-enhancements-to-the-Azure-AD-combined-MFA-and-password/ba-p/354271). This means that your users will no longer be able to use the old experience.
 
-For more information about the enhanced security info experience, see our [admin documentation](https://aka.ms/securityinfodocs) and our [user documentation](https://aka.ms/securityinfoguide).
+For more information about the enhanced security info experience, see our [admin documentation](https://aka.ms/securityinfodocs) and our [user documentation](https://aka.ms/securityinfoguide).
 
 #### To turn on this new experience, you must:
 
 1. Sign in to the Azure portal as a Global Administrator or User Administrator.
 
-2. Go to **Azure Active Directory > User settings > Manage settings for access panel preview features**.
+2. Go to **Azure Active Directory > User settings > Manage settings for access panel preview features**.
 
 3. In the **Users can use preview features for registering and managing security info - enhanced** area, select **Selected**, and then either choose a group of users or choose **All** to turn this feature on for all users in the tenant.
 

articles/active-directory/governance/entitlement-management-organization.md

@@ -42,6 +42,10 @@ How users from the Azure AD directory or domain will authenticate depends on the
 - [Direct federation](../b2b/direct-federation.md)
 - [One-time passcode](../b2b/one-time-passcode.md) (domain)
 
+For a demonstration of how to add a connected organization, watch the following video:
+
+>[!VIDEO https://www.microsoft.com/videoplayer/embed/RE4dskS]
+
 ## Add a connected organization
 
 Follow these steps to add an external Azure AD directory or domain as a connected organization.

articles/active-directory/saas-apps/jiramicrosoft-tutorial.md

@@ -57,8 +57,8 @@ To get started, you need the following items:
 
 ## Supported versions of JIRA
 
-* JIRA Core and Software: 6.4 to 8.2.4
-* JIRA Service Desk 3.0.0 to 4.2.1
+* JIRA Core and Software: 6.4 to 8.5.1
+* JIRA Service Desk 3.0.0 to 4.5.1
 * JIRA also supports 5.2. For more details, click [Microsoft Azure Active Directory single sign-on for JIRA 5.2](jira52microsoft-tutorial.md)
 
 > [!NOTE]