Download Microsoft Azure AD
Author: g | 2025-04-24
Download Azure AD Connect. Download Azure AD Connect for free. Download Microsoft Azure Active Directory Connect from the Microsoft Download Center. In this article, we will install Azure AD Connect version 2.1.1.0, which is the latest. Azure AD connect release notes. Microsoft keeps a changelog for Azure AD Connect.
Download Microsoft Azure AD Connect by Microsoft - Software
Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Active Directory Rights Management Services Mobile Device Extension Article08/02/2022 In this article -->You can download the Active Directory Rights Management Services (AD RMS) mobile device extension from the Microsoft Download Center and install this extension on top of an existing AD RMS deployment. This lets users protect and consume sensitive data when their device supports the latest API-enlightened apps. For example, users can do the following on their mobile devices:Use the Azure Information Protection app to consume protected text files in different formats (including .txt, .csv, and .xml).Use the Azure Information Protection app to consume protected image files (including .jpg, .gif, and .tif).Use the Azure Information Protection app to open any file that has been generically protected (.pfile format).Use the Azure Information Protection app to open an Office file (Word, Excel, PowerPoint) that is a PDF copy (.pdf and .ppdf format).Use the Azure Information Protection app to open protected email messages (.rpmsg) and protected PDF files on Microsoft SharePoint.Use an AIP-enlightened PDF viewer for cross-platform viewing or to open PDF files that were protected with any AIP-enlightened application.Use your internally developed AIP-enlightened apps that were written by using the MIP SDK.NoteYou can download the Azure Information Protection app from the Microsoft Rights Management page of the Microsoft website. For information about other apps that are supported with the mobile device extension, see the table in the Applications page from this documentation. For more information about the different file types that RMS supports, see the Supported file types and file name extensions section from the Rights Management sharing application administrator guide.ImportantBe sure to read and configure the prerequisites before you install the mobile device extension.For additional information, download the "Microsoft Azure Information Protection" white paper and accompanying scripts from the Microsoft Download Center.Before you install the AD RMS mobile device extension, make sure the following dependencies are in place.RequirementMore informationAn existing AD RMS deployment on Windows Server 2019, 2016, 2012 R2, or 2012, that includes the following: - Your AD RMS cluster must be accessible from the Internet. - AD RMS must be using a full Microsoft SQL Server-based database on a separate server and not the Windows Internal Database that is often used for testing on the same server. - The account that you will use to install the mobile device extension must have sysadmin rights for the SQL Server instance that you're using for AD RMS. - The AD RMS servers must be configured to use SSL/TLS with a valid x.509 certificate that is trusted by the mobile device clients. - If the Before reading this section, please read the following important note.Depending on the user location, there are four scenarios for the cloud MFA service:Microsoft Entra ID and on-premises AD using federation with AD FS (is required for SSO)Microsoft Entra ID and on-premises AD using DirSync, Azure AD Sync, Azure AD Connect - no password syncMicrosoft Entra ID and on-premises AD using DirSync, Azure AD Sync, Azure AD Connect - with password syncOn-premises Active DirectoryAn Azure account with Global Administrator role is required to download and activate MFA Server. Syncing with Microsoft Entra ID (via AD Connect) or a custom DNS domain aren't required to setup an MFA Server which runs exclusively on-premises.Users need to be imported into MFA Server and be configured for MFA authentication.Parallels RAS authenticates users with MFA Server using the RADIUS second level authentication provider. MFA Server thus needs to be configured to allow RADIUS client connections from the RAS server.The authentication process goes through the following stages:In stage 2 the user can be authenticated using either RADIUS or Windows AD. A prompt to enter the credentials twice (in stage 1 and 6) is avoided by enabling the option to forward the password.Help with Download - Microsoft Azure AD Connect
Splashtop supports logging into my.splashtop.com and Splashtop Business app using the same credentials as your SAML 2.0 identity provider. Please follow the below instructions to get the app from Microsoft Entra ID/Azure AD console.Get the app on Microsoft Entra ID/Azure AD console1. Log in Azure AD console. Select Enterprise applications2. Click "+ New application".3. Search Splashtop from the gallery then add.5. After adding the app, select Set up single sign on, then select SAML.6. Edit Basic SAML configuration.Identifier (Entity ID): URL (Assertion Consumer Service URL): on URL: (There are patterns under each three field which you can copy then paste to the corresponding fields.)Leave others without changes.7. Edit User Attributes & Claims.Unique User Identifier: Keep the default value "user.userprincipalname", or modify it to the attribute you use to match the user's email address to their Splashtop account, such as "user.mail". Ensure the selected attribute corresponds to the email address associated with the user's Splashtop account.( The value has to be the email address associated with the Splashtop account).8. Done!***For JIT provisioning, please add a group claim:1. In the set up SSO app on Microsoft Entra ID/Azure AD, go to Single sign-on page.2. On the Attributes Claims block, click Edit.3. On the Edit page, click Add a group claim.4. On the Group Claims setup, select Security Groups.5. Click Save.6. Done!Add user/group to the created appClick Add user/group to add users to the created enterprise application so the user can use SSO feature.Apply for an SSO method from my.splashtop.comNow you have the Login URL, Microsoft Entra ID/Azure AD Identifier, and Download Certificate (Base64). Please follow below instruction to insert the info on our web portal (my.splashtop.com) to apply for enabling the SSO with Microsoft Entra ID/Azure AD. downloading Certificate (Base64), please edit the cert file with a text editor, then copy the contents to insert on my.splashtop.com.Additional Resources:Microsoft Tutorial: Microsoft Entra single sign-on (SSO) integration with SplashtopIf interested you can provision with SCIM for Microsoft Entra ID/Azure AD.See this article: Provisioning setup - Microsoft Entra ID/Azure AD (SCIM). Download Azure AD Connect. Download Azure AD Connect for free. Download Microsoft Azure Active Directory Connect from the Microsoft Download Center. In this article, we will install Azure AD Connect version 2.1.1.0, which is the latest. Azure AD connect release notes. Microsoft keeps a changelog for Azure AD Connect. Download Azure AD Connect. Download Azure AD Connect for free. Download Microsoft Azure Active Directory Connect from the Microsoft Download Center. In this article, we will install Azure AD Connect version 2.1.1.0, which is theMicrosoft Azure AD Connect - Help Download :
Can find a comparison of Azure AD editions on Microsoft’s website here.But you should note that the free edition of Azure AD doesn’t include all the features of Azure AD Join. To get the features listed below, you’ll need Azure AD P1 or P2 licenses:Mobile Device Management (MDM) autoenrollmentLocal admin policy customizationSelf-service BitLocker recoveryEnterprise state roaming (ESR)The account I was using to join Windows 10 to Azure AD was assigned a Microsoft 365 Business Standard license. That means there is no Microsoft Intune license included with the Microsoft 365 subscription. To get Intune, which is Microsoft’s MDM service, I would need to either license Intune separately or upgrade to a Microsoft 365 Business Premium license. Nevertheless, I should be able to perform an Azure AD join using a Microsoft 365 Business Standard account.Disable MDM autoenrollmentAfter some digging around on the Internet, I found that the issue is likely connected to MDM autoenrollment. As the Microsoft 365 Business Standard account isn’t licensed for Intune, Azure AD join fails because the account is enabled for MDM autoenrollment.The solution is to disable MDM autoenrollment for the account, or all accounts, in the Azure AD tenant. But hold up. Without an Azure AD P1 or P2 license, there is no access to modify MDM autoenrollment settings.This led me to call Microsoft support. I was advised to assign a trial Azure AD Premium license to an account and turn off MDM autoenrollment. So, that’s what I did. And hey presto, I was able to join the Windows 10 device to Azure AD with no errors. To be clear, the work or school account used to join Windows 10 to Azure AD does not need an Azure AD Premium license. The license is only required to modify the MDM enrollment settings.To disable MDM autoenrollment, follow these Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Article08/17/2024 In this article -->This article provides answers to frequently asked questions about migrating from Azure Active Directory (Azure AD) Graph to Microsoft Graph.Azure AD Graph offers access to only Microsoft Entra ID (formerly Azure AD) services. Microsoft Graph offers a single unified endpoint to access Microsoft Entra identity and network access family of services and other Microsoft services such as Microsoft Teams, Microsoft Exchange, Microsoft Intune, and much more.Microsoft Graph is also more secure and resilient than Azure AD Graph. For this reason, Azure AD Graph is currently in a phased retirement cycle as we move all investments to Microsoft Graph. Migrate to Microsoft Graph to avoid loss of existing functionality and to access new features and capabilities.Follow these steps to identify apps with a dependency on Azure AD Graph:Option 1: Check the Microsoft Entra recommendationsSign in to an API client such as Graph Explorer with the required permissions and roles to view Microsoft Entra ID recommendations. Run the List recommendations Microsoft Graph API to retrieve the list of apps and service principals that use Azure AD Graph.Option 2: Use the appId of the app to identify its API permissionsStep 1: Scan the application source codeIf you own an application's source code, search for the URI in the code. This value is the Azure AD Graph endpoint and apps that call this endpointMicrosoft Office 365 / Azure AD
Protection DC Agent, installed on the DC. This Agent then validate if the password is compliance with the locally stored Azure password policy.The Agent on the DC every 1h locate via the SCP (Service Connection Point) in the forest the Azure AD Password Protection Proxy Service to download a fresh copy of the Azure password policy.The Agent on the DC receives the new version of the Azure password policy from the proxy service and stores it in the Sysvol enabling this new policy to be replicated to all other DCs in the same domain.The Azure Password policies are stored in Sysvol as shown here:It is not necessary that all the DCs are able to comunicate with the Azure AD Password Protection Proxy Server, if you have a very complex Active Directory environments, you can configure a minimum of one DC per domain to be able to connect to the AAD Password Protection Proxy Servers, and the other DCs will take the new policy from the Sysvol replication. However, on these DCs you will see some warning of this type:Log Name: Microsoft-AzureADPasswordProtection-DCAgent/AdminSource: Microsoft-AzureADPasswordProtection-DCAgentDate: 15/05/2019 23:37:39Event ID: 30018Task Category: NoneLevel: WarningKeywords: User: SYSTEMComputer: ITDC01.IT.CONTOSO.COMDescription:One or more Azure AD Password Protection Proxy servers were found in the forest but this machine was unable to establish network connectivity to any of them. This operation will be run periodically and may succeed in future attempts This may be an expected and benign condition depending on how the network environment is configured. This domain controller may be able to obtain updated password policies via sysvol replication if other domain controllers do have proxy connectivity.How can I deploy the Azure AD Password Protection?The following is a an example of a simple scenario to understand how-to deploy this feature:Since your DCs never talk directly with Azure you need at least 2 Azure AD Password Protection Proxy Server per Forest for high availability and should be placed in the Root Domain. The Azure AD Password Protection Proxy Servers must be Windows Server 2012R2 or above.Download the Azure AD Password Protection software (Proxy and DC Agent): Be sure to haveAdding Microsoft Azure Cloud Monitoring
Reports offer invaluable insights into user properties, external users, licenses, and MFA statuses. Overwhelming the native tools, this functionality empowers admins to monitor Azure AD information with nicely formatted reports. The Azure AD auditing tool by AdminDroid allows admins to closely monitor changes in user profiles, logins, MFA, passwords, groups, and admin roles, providing real-time updates to fortify organizational security. Here’s the surprise! You may find it hard to believe, but AdminDroid Azure AD management allows free access to 120+ reports for MS Entra auditing and reporting. AdminDroid doesn’t stop at Entra ID management; it extends to and connects with all Microsoft 365 services for comprehensive reporting. In total, the tool offers an impressive collection of 1800+ reports and 30+ dashboards, all accessible with a 15-day premium edition. Download the AdminDroid M365 reporting tool today and simplify Microsoft 365 management effortlessly! Overall, we have aimed to provide comprehensive guidance to reset and manage Microsoft 365 user passwords using PowerShell. Contributing to user management in Microsoft 365, we trust this blog serves as a valuable resource to strengthen user password protection. Your thoughts and comments are highly encouraged; feel free to share your insights in the comments section.. Download Azure AD Connect. Download Azure AD Connect for free. Download Microsoft Azure Active Directory Connect from the Microsoft Download Center. In this article, we will install Azure AD Connect version 2.1.1.0, which is the latest. Azure AD connect release notes. Microsoft keeps a changelog for Azure AD Connect. Download Azure AD Connect. Download Azure AD Connect for free. Download Microsoft Azure Active Directory Connect from the Microsoft Download Center. In this article, we will install Azure AD Connect version 2.1.1.0, which is theAzure AD limitations - Microsoft Q A
Use Azure AD Graph. Record the value of the affected app's appId.Step 2: Call the "Get application" API to read the app's API permissionsSign in to an API client such as Graph Explorer with at least the Application Developer Microsoft Entra role and granted the Application.Read.All delegated permission.Call the Get application API using the appId you retrieved in Step 1 and read the requiredResourceAccess property. The following properties show the permission details:The requiredResourceAccess > resourceAppId property has the ID 00000002-0000-0000-c000-000000000000 for Azure AD Graph.The requiredResourceAccess > resourceAccess property lists the ID and type of Azure AD Graph permissions the app uses. Use the Permissions differences between Azure AD Graph and Microsoft Graph mapping guide to know the Azure AD Graph permission names.Use the following four methods to identify apps in your tenant with a dependency on Azure AD Graph. Method 1 and 2 identify your apps that use Azure AD Graph based on the actual app activities while method 3 and 4 use static app configuration and consent status. You can combine these methods to find apps that have a dependency on Azure AD Graph.Method 1: Through network proxy logsCheck your network server traffic logs through a filter proxy for any apps calling the endpoint. These apps use Azure AD Graph.Method 2: Check the Microsoft Entra recommendationsSign in to the Microsoft Entra admin center with privileges to view Microsoft Entra ID recommendations. The following least privileged roles are supported for this operation: Reports Reader, and Security Reader, and Global Reader.ExpandComments
Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Active Directory Rights Management Services Mobile Device Extension Article08/02/2022 In this article -->You can download the Active Directory Rights Management Services (AD RMS) mobile device extension from the Microsoft Download Center and install this extension on top of an existing AD RMS deployment. This lets users protect and consume sensitive data when their device supports the latest API-enlightened apps. For example, users can do the following on their mobile devices:Use the Azure Information Protection app to consume protected text files in different formats (including .txt, .csv, and .xml).Use the Azure Information Protection app to consume protected image files (including .jpg, .gif, and .tif).Use the Azure Information Protection app to open any file that has been generically protected (.pfile format).Use the Azure Information Protection app to open an Office file (Word, Excel, PowerPoint) that is a PDF copy (.pdf and .ppdf format).Use the Azure Information Protection app to open protected email messages (.rpmsg) and protected PDF files on Microsoft SharePoint.Use an AIP-enlightened PDF viewer for cross-platform viewing or to open PDF files that were protected with any AIP-enlightened application.Use your internally developed AIP-enlightened apps that were written by using the MIP SDK.NoteYou can download the Azure Information Protection app from the Microsoft Rights Management page of the Microsoft website. For information about other apps that are supported with the mobile device extension, see the table in the Applications page from this documentation. For more information about the different file types that RMS supports, see the Supported file types and file name extensions section from the Rights Management sharing application administrator guide.ImportantBe sure to read and configure the prerequisites before you install the mobile device extension.For additional information, download the "Microsoft Azure Information Protection" white paper and accompanying scripts from the Microsoft Download Center.Before you install the AD RMS mobile device extension, make sure the following dependencies are in place.RequirementMore informationAn existing AD RMS deployment on Windows Server 2019, 2016, 2012 R2, or 2012, that includes the following: - Your AD RMS cluster must be accessible from the Internet. - AD RMS must be using a full Microsoft SQL Server-based database on a separate server and not the Windows Internal Database that is often used for testing on the same server. - The account that you will use to install the mobile device extension must have sysadmin rights for the SQL Server instance that you're using for AD RMS. - The AD RMS servers must be configured to use SSL/TLS with a valid x.509 certificate that is trusted by the mobile device clients. - If the
2025-04-16Before reading this section, please read the following important note.Depending on the user location, there are four scenarios for the cloud MFA service:Microsoft Entra ID and on-premises AD using federation with AD FS (is required for SSO)Microsoft Entra ID and on-premises AD using DirSync, Azure AD Sync, Azure AD Connect - no password syncMicrosoft Entra ID and on-premises AD using DirSync, Azure AD Sync, Azure AD Connect - with password syncOn-premises Active DirectoryAn Azure account with Global Administrator role is required to download and activate MFA Server. Syncing with Microsoft Entra ID (via AD Connect) or a custom DNS domain aren't required to setup an MFA Server which runs exclusively on-premises.Users need to be imported into MFA Server and be configured for MFA authentication.Parallels RAS authenticates users with MFA Server using the RADIUS second level authentication provider. MFA Server thus needs to be configured to allow RADIUS client connections from the RAS server.The authentication process goes through the following stages:In stage 2 the user can be authenticated using either RADIUS or Windows AD. A prompt to enter the credentials twice (in stage 1 and 6) is avoided by enabling the option to forward the password.
2025-03-25Splashtop supports logging into my.splashtop.com and Splashtop Business app using the same credentials as your SAML 2.0 identity provider. Please follow the below instructions to get the app from Microsoft Entra ID/Azure AD console.Get the app on Microsoft Entra ID/Azure AD console1. Log in Azure AD console. Select Enterprise applications2. Click "+ New application".3. Search Splashtop from the gallery then add.5. After adding the app, select Set up single sign on, then select SAML.6. Edit Basic SAML configuration.Identifier (Entity ID): URL (Assertion Consumer Service URL): on URL: (There are patterns under each three field which you can copy then paste to the corresponding fields.)Leave others without changes.7. Edit User Attributes & Claims.Unique User Identifier: Keep the default value "user.userprincipalname", or modify it to the attribute you use to match the user's email address to their Splashtop account, such as "user.mail". Ensure the selected attribute corresponds to the email address associated with the user's Splashtop account.( The value has to be the email address associated with the Splashtop account).8. Done!***For JIT provisioning, please add a group claim:1. In the set up SSO app on Microsoft Entra ID/Azure AD, go to Single sign-on page.2. On the Attributes Claims block, click Edit.3. On the Edit page, click Add a group claim.4. On the Group Claims setup, select Security Groups.5. Click Save.6. Done!Add user/group to the created appClick Add user/group to add users to the created enterprise application so the user can use SSO feature.Apply for an SSO method from my.splashtop.comNow you have the Login URL, Microsoft Entra ID/Azure AD Identifier, and Download Certificate (Base64). Please follow below instruction to insert the info on our web portal (my.splashtop.com) to apply for enabling the SSO with Microsoft Entra ID/Azure AD. downloading Certificate (Base64), please edit the cert file with a text editor, then copy the contents to insert on my.splashtop.com.Additional Resources:Microsoft Tutorial: Microsoft Entra single sign-on (SSO) integration with SplashtopIf interested you can provision with SCIM for Microsoft Entra ID/Azure AD.See this article: Provisioning setup - Microsoft Entra ID/Azure AD (SCIM)
2025-03-25Can find a comparison of Azure AD editions on Microsoft’s website here.But you should note that the free edition of Azure AD doesn’t include all the features of Azure AD Join. To get the features listed below, you’ll need Azure AD P1 or P2 licenses:Mobile Device Management (MDM) autoenrollmentLocal admin policy customizationSelf-service BitLocker recoveryEnterprise state roaming (ESR)The account I was using to join Windows 10 to Azure AD was assigned a Microsoft 365 Business Standard license. That means there is no Microsoft Intune license included with the Microsoft 365 subscription. To get Intune, which is Microsoft’s MDM service, I would need to either license Intune separately or upgrade to a Microsoft 365 Business Premium license. Nevertheless, I should be able to perform an Azure AD join using a Microsoft 365 Business Standard account.Disable MDM autoenrollmentAfter some digging around on the Internet, I found that the issue is likely connected to MDM autoenrollment. As the Microsoft 365 Business Standard account isn’t licensed for Intune, Azure AD join fails because the account is enabled for MDM autoenrollment.The solution is to disable MDM autoenrollment for the account, or all accounts, in the Azure AD tenant. But hold up. Without an Azure AD P1 or P2 license, there is no access to modify MDM autoenrollment settings.This led me to call Microsoft support. I was advised to assign a trial Azure AD Premium license to an account and turn off MDM autoenrollment. So, that’s what I did. And hey presto, I was able to join the Windows 10 device to Azure AD with no errors. To be clear, the work or school account used to join Windows 10 to Azure AD does not need an Azure AD Premium license. The license is only required to modify the MDM enrollment settings.To disable MDM autoenrollment, follow these
2025-04-17Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Article08/17/2024 In this article -->This article provides answers to frequently asked questions about migrating from Azure Active Directory (Azure AD) Graph to Microsoft Graph.Azure AD Graph offers access to only Microsoft Entra ID (formerly Azure AD) services. Microsoft Graph offers a single unified endpoint to access Microsoft Entra identity and network access family of services and other Microsoft services such as Microsoft Teams, Microsoft Exchange, Microsoft Intune, and much more.Microsoft Graph is also more secure and resilient than Azure AD Graph. For this reason, Azure AD Graph is currently in a phased retirement cycle as we move all investments to Microsoft Graph. Migrate to Microsoft Graph to avoid loss of existing functionality and to access new features and capabilities.Follow these steps to identify apps with a dependency on Azure AD Graph:Option 1: Check the Microsoft Entra recommendationsSign in to an API client such as Graph Explorer with the required permissions and roles to view Microsoft Entra ID recommendations. Run the List recommendations Microsoft Graph API to retrieve the list of apps and service principals that use Azure AD Graph.Option 2: Use the appId of the app to identify its API permissionsStep 1: Scan the application source codeIf you own an application's source code, search for the URI in the code. This value is the Azure AD Graph endpoint and apps that call this endpoint
2025-04-06Protection DC Agent, installed on the DC. This Agent then validate if the password is compliance with the locally stored Azure password policy.The Agent on the DC every 1h locate via the SCP (Service Connection Point) in the forest the Azure AD Password Protection Proxy Service to download a fresh copy of the Azure password policy.The Agent on the DC receives the new version of the Azure password policy from the proxy service and stores it in the Sysvol enabling this new policy to be replicated to all other DCs in the same domain.The Azure Password policies are stored in Sysvol as shown here:It is not necessary that all the DCs are able to comunicate with the Azure AD Password Protection Proxy Server, if you have a very complex Active Directory environments, you can configure a minimum of one DC per domain to be able to connect to the AAD Password Protection Proxy Servers, and the other DCs will take the new policy from the Sysvol replication. However, on these DCs you will see some warning of this type:Log Name: Microsoft-AzureADPasswordProtection-DCAgent/AdminSource: Microsoft-AzureADPasswordProtection-DCAgentDate: 15/05/2019 23:37:39Event ID: 30018Task Category: NoneLevel: WarningKeywords: User: SYSTEMComputer: ITDC01.IT.CONTOSO.COMDescription:One or more Azure AD Password Protection Proxy servers were found in the forest but this machine was unable to establish network connectivity to any of them. This operation will be run periodically and may succeed in future attempts This may be an expected and benign condition depending on how the network environment is configured. This domain controller may be able to obtain updated password policies via sysvol replication if other domain controllers do have proxy connectivity.How can I deploy the Azure AD Password Protection?The following is a an example of a simple scenario to understand how-to deploy this feature:Since your DCs never talk directly with Azure you need at least 2 Azure AD Password Protection Proxy Server per Forest for high availability and should be placed in the Root Domain. The Azure AD Password Protection Proxy Servers must be Windows Server 2012R2 or above.Download the Azure AD Password Protection software (Proxy and DC Agent): Be sure to have
2025-04-06