Merge pull request #7912 from RavennMSFT/patch-2

Update Intro section for AADJ

Author: GitHubber17

articles/active-directory/device-management-introduction.md

@@ -71,20 +71,23 @@ The goal of Azure AD joined devices is to simplify:
 
 
 These goals are accomplished by providing your users with a self-service experience for getting work-owned devices under the control of Azure AD.  
-**Azure AD Join** is intended for organizations that are cloud-first / cloud-only. These are typically small- and medium-sized businesses that do not have an on-premises Windows Server Active Directory infrastructure. 
+**Azure AD Join** is intended for organizations that desire to be cloud-first or cloud-only. There is no restriction on the size or type of organizations that can deploy Azure AD Join. Azure AD Join works well even in an hybrid environment and can enable access to on-premise apps and resources.
 
 Implementing Azure AD joined devices provides you with the following benefits:
 
 - **Single-Sign-On (SSO)** to your Azure managed SaaS apps and services. Your users don’t see additional authentication prompts when accessing work resources. The SSO functionality is even when they are not connected to the domain network available.
 
 - **Enterprise compliant roaming** of user settings across joined devices. Users don’t need to connect a Microsoft account (for example, Hotmail) to see settings across devices.
 
-- **Access to Windows Store for Business** using AD account. Your users can choose from an inventory of applications pre-selected by the organization.
+- **Access to Windows Store for Business** using an Azure AD account. Your users can choose from an inventory of applications pre-selected by the organization.
 
 - **Windows Hello** support for secure and convenient access to work resources.
 
 - **Restriction of access** to apps from only devices that meet compliance policy.
 
+- **Seamless access to on-premise resources** when the device has line of sight to the on-premises domain controller.
+
+
 While Azure AD join is primarily intended for organizations that do not have an on-premises Windows Server Active Directory infrastructure, you can certainly also use it in scenarios where:
 
 - You can’t use an on-premises domain join, for example, if you need to get mobile devices such as tablets and phones under control.