Entra Exporter Tool – Effortlessly Backup Microsoft Entra ID Configurations

When it comes to identity and access management, there’s no doubt that Entra and Azure AD B2C take center stage💯. These guardians stand as a holistic defense against threats, fortifying your security of Microsoft 365. By the way, the key to these defenses lies in their configurations.

So, any misconfiguration in these settings could open doors for potential attackers. Therefore, regular monitoring of the Entra settings is crucial for an organization.

To get insights into Entra settings, you might have initially considered Azure AD Exporter. However, it has been deprecated from the PowerShell gallery. So, what’s the next step for obtaining those insights🤔? No worries! The Entra Exporter module steps in to fill the gap. This PowerShell module exports a local copy of Entra and B2C settings configuration similar to the Azure AD Exporter.

Let’s learn how to efficiently manage Entra and Azure B2C settings with the Entra Exporter PowerShell module.

As the Entra Exporter module exports JSON files of B2C and Entra settings, it becomes the ideal solution for admins to keep backup. Here’s a list of specific reasons why the Entra Exporter is a compelling tool to consider:

• Backup and Versioning: The Entra Exporter’s ability to export Entra settings to JSON files serves as a robust backup mechanism. This becomes valuable in scenarios of data loss or accidental changes. With this feature, you can restore configurations to previous states, ensuring data integrity.
• Nightly Scheduled Task: The Entra Exporter module seamlessly can be integrated with Task Scheduler. This eliminates the need for manual effort, as it facilitates the execution of the cmdlet at scheduled intervals.
• Integration with DevOps Pipelines: Seamlessly integrating with DevOps pipelines, the Entra Exporter maintains an audit trail of setting changes, bolstering transparency and accountability. Moreover, this historical configuration view simplifies troubleshooting and debugging, enabling you to pinpoint changes that might have led to unexpected behavior.
• Replication of Settings: Leveraging the exported JSON files, you can easily migrate or replicate configuration settings across various tenants. This simplifies the process of creating new environments with consistent configurations, reducing the potential for errors and inconsistencies.
• Documentation Purpose: The JSON files exported by the Entra Exporter serve as documentation of configuration settings. This documentation is especially valuable for new administrators who can quickly grasp the Entra configurations and can modify changes according to the need.

Thus, the Entra Exporter module, equipped with scheduling capability and integration functionality, empowers you to keep an eye on Azure settings without interruption.

Now, let’ get into the steps to install Entra Exporter PowerShell module.

To export Entra and B2C settings, you need to download and install Entra Exporter first. You can open the Windows PowerShell in administrator mode and can install the module using the following cmdlet. By the way, it is recommended to use PowerShell 7 or above to achieve optimal output.

After confirming the prompt, the installation process for the module will be completed within seconds.

Once the module installation is finished, the subsequent step involves connecting your M365 environment. You can establish this connection by executing the following cmdlet.

Upon executing the aforementioned cmdlet, you’ll be prompted to provide the necessary consent. By granting consent, you enable access to your Microsoft Entra.

Note: Instead of using Connect-EntraExporter , you can use Connect-MgGraph with the following scopes for authentication. Following successful authentication through Connect-MgGraph, you can seamlessly proceed to employ the export cmdlets for your tasks.

Once you’ve established a successful connection with the tenant, you can utilize the following cmdlet to export Entra and B2C settings. However, it’s important to note that the given cmdlet exports fundamental Entra settings alone. Because the below default cmdlet is intentionally designed to prioritize the settings and objects that administrators use the most. So, details about the static groups, group memberships, applications, service principals, users, PIM are not exported by this default cmdlet.

This cmdlet will export the list of settings and objects showed in the below screenshot.

To retrieve additional Entra settings, you need to run the Export-Entra cmdlet with “All” parameter.

Here you can be able to view the additional settings like privileged access, groups, identity governance, etc.

Note: This module exports all settings that can be accessed via the Microsoft Graph API, with the exception of specific settings and objects such as Enterprise State Roaming and a few others that are currently not supported by the Graph API. As this tool exports configurations via the MS Graph API, its activities are captured in the Microsoft Graph activity logs.

Since this module includes a filtering capability, you can utilize it to generate JSON files containing specific Entra objects, such as groups, PIM configurations. Instead of scouring through an extensive array of Entra settings, you can focus solely on the settings you require.

To get details of specific settings/objects, you can run the given cmdlet with the ‘Type’ parameter like below.

Note: Currently this module supports the few valid ‘Types’ alone. To know the valid Types, you can run the below cmdlet.

We have illustrated the utilization of the cmdlet by showcasing its execution with several valid Types, aiming to provide you with a clear example.

• Gain service principal information via Entra Exporter
• Export App registration details with Entra Exporter Module
• Monitor directory roles using Entra Exporter
• Export M365 license details into JSON file
• Review tenant policies using Entra Exporter
• Export M365 users using Entra Exporter module
• Review Microsoft 365 groups with Entra Exporter
• Extract Conditional Access policy details to JSON files
• Get details of PIM settings with Entra Exporter

Service Principals are the secure identities used by applications, and services to authenticate and access Entra. So, you need to monitor the service principal settings regularly to prevent malicious attacks in the organization.

To get details of the service principals created in your Microsoft 365 environment, you can make use of the cmdlet below.

This will export all the details of Service Principals in JSON format. Added to that, you can effectively monitor service principal sign-ins to track daily application usage and resource access in the organization. By observing this, you can easily identify unusual sign-in activities in your organization.

Sample JSON Format:

To retrieve the details of the Azure AD app registrations, simply run the default export cmdlet with “Applications” Type like below. This will export all the registered applications to your tenant along with the details like application Id, app creation time, OAuth2Permissions, token issuance, etc.

Sample JSON Format:

Reviewing O365 users with Entra roles is crucial due to the possibility of misconfigurations in role assignments. Such misconfigurations can lead to security vulnerabilities in Microsoft 365. So, you can use the below cmdlet to review Azure AD role assignments in your organization.

Sample JSON File:

The given cmdlet primarily provides the user’s ID associated with the designated Azure AD role. However, recognizing users solely by their IDs might not be optimal for quick identification. To address this, you can use the PS script provided in the blog to export Office 365 admin role report. The exported report will display the name, email address, and other relevant information of users with Entra roles.

By exporting license data, you gain a clear and comprehensive overview of your organization’s license details. This will help you to check the license availability in your organization.

You can use the below PowerShell cmdlet to export license details using “SKU” Type.

Sample JSON File:

By the way, you can make use of the PowerShell script to get detailed Microsoft 365 license report with subscription name, subscribed date, subscription type, license expiry date, subscription status and more. These comprehensive insights help you to renew your licenses in a timely manner.

You can gain insights into policies like authentication method policy, token issuance policies, token lifetime policies using the Entra Exporter.

To export tenant policy configurations, you can use the below cmdlet.

Sample JSON File:

Reviewing Microsoft 365 user details is crucial to maintain security and compliance within the organization. But manually navigating through user accounts in the admin center to find specific data is time-consuming. However, you can significantly reduce this effort by employing Entra Exporter to export all user account details into a JSON format.

To do so, you can utilize the below PowerShell cmdlet.

Sample JSON File:

Monitoring Microsoft 365 groups’ details and configurations is crucial for enhancing data security and access control. You can use the below Entra Exporter cmdlet to export Microsoft 365 groups.

The exported JSON format contains details like groupId, membership type of the group, mailbox status, guest user access permission, group expiration date, and various other relevant information.

Sample JSON File:

Additionally, you can utilize the PowerShell script provided in the blog to export a more detailed Microsoft 365 group report. This script enables you to gain insights into group memberships, group sizes, member counts within each group, identification of empty groups, and more.

To keep track of changes in your Conditional Access policies and named locations, you can leverage the power of Entra Exporter PowerShell module.

The Entra Exporter cmdlets below enables you to export Conditional Access policy details into JSON files. These files serve as a valuable resource for reviewing and auditing your security settings over time.

Sample JSON File:

PIM enables you to manage access to critical resources in your organization, with its three components: Microsoft Entra roles, Azure roles, and PIM for groups. So, it is required to have a constant look into the PIM settings for effective access control.

Thus, you can derive a copy of PIM settings anytime by simply running the below cmdlet.

Sample JSON File:

Along with continuous monitoring of PIM settings, you can enhance the security of PIM groups by integrating PIM with Conditional Access.

Along with the task scheduler, this module paves the way for the constant reviewing of Entra settings. However, the superior approach is to integrate the module with the DevOps pipelines. This approach preserves a comprehensive history of Entra settings’ changes. Moreover, it enhances the organization and efficiency of managing your Entra and Azure AD B2C configuration settings.

Also, instead of spending your efforts and time in manual exporting and pushing files to the repository, you can make use of Git commands. This will save you time by automating the process, thereby maintaining a history of settings’ changes efficiently.

To do so, follow the steps below to fulfill the prerequisites for pushing the changes to the remote repository.

• Install Git on your local device and open Git CMD after confirming consents.
• Use the command mkdir <folderName> to create a repository folder.
• Navigate to this folder using cd LocalGit.
• Create a Git repository with mkdir <Repository name>.

Now, run the code below to integrate the JSON file with Git.

I hope you have learned about the useful PowerShell module which will help you to export Entra and Azure AD B2C settings with just simple cmdlets. Wait! There is a further beneficial tool- “Microsoft365DSC“. You can automate M365 tenant settings with Microsoft365DSC tool across various services Entra ID, SharePoint, Exchange Online, and more, with ease.

Furthermore, feel free to reach us in the comment section for any assistance.