[Feature Request]: See Entra ID Connect Details

May 13, 2025 by ADMIN 48 views

**Feature Request: Enhancing Entra ID Connect Details for MSPs**

Introduction

As a Microsoft Partner, managing multiple client configurations can be a daunting task. The ability to see which user accounts are synced via Entra ID Connect and which are located only in the cloud is crucial for efficient management. Currently, this information is not readily available, leading to confusion and wasted time for technicians. This feature request aims to address this issue by providing a column to display Entra ID Connect details, including user sync status, last successful sync, current sync agent version, server name, and service account.

Problem Statement

As an MSP, we face various configurations for different clients, making it challenging to determine which users are only in the cloud and which are Entra ID synced. The Entra ID synced users cannot be fully managed through 365, requiring technicians to access the domain controller for certain actions. This can lead to errors or failed changes. Additionally, being able to see other Entra ID Connect details, such as the last successful sync, current sync agent version, server name, and the service account, would be highly beneficial.

Current Workaround

While a similar request was closed due to the requester not being a paid user, as a paying user, I would like to request the same details and expand the request to include user sync status. The original request was https://github.com/KelvinTegelaar/CIPP/issues/3823 on March 19th.

Benefits for MSPs

Having access to Entra ID Connect details would significantly improve the efficiency of our technicians. If I only dealt with one client, I would quickly memorize if they were using Entra ID Sync. However, as an MSP, I have to deal with hundreds of clients. Putting this information in a spot that's easy for my technicians to see allows for them to use the correct tools the first time and avoids them wasting time working through the wrong tool.

Improved Reporting and Alerting

This feature would also allow me to better report or alert on Entra ID Connect issues without having to log into each client's tenant or server. By having access to the last successful sync, current sync agent version, server name, and service account, I can create more accurate and timely alerts, ensuring that issues are caught and resolved promptly.

Value or Importance

This feature would put sync status right in front of the technicians so they can see if the user can be edited in 365/CIPP or if they need to make changes from the domain controller. This would prevent technicians from wasting time attempting to edit a user and likely getting errors or at least failed changes.

Audit and Compliance

Having the server agent version and related info would enable us to better audit across our clients without having to log into servers or the Entra ID admin portal to see those details. This would improve our ability to meet compliance requirements and ensure that our clients' data is secure.

Enhanced Alerting

Having the last successful sync in CIPP would make it easier to create an alert to tell us if a sync hasn't occurred recently. This can be critical to catching issues in a timely manner, ensuring that our clients' data is up-to-date and secure.

PowerShell Commands (Optional)

While PowerShell commands are not provided in this request, having access to Entra ID Connect details through the CIPP interface would eliminate the need for manual logging into each client's tenant or server. This would streamline our workflow and reduce the risk of errors.

Conclusion

Introduction

As a Microsoft Partner, managing multiple client configurations can be a daunting task. The ability to see which user accounts are synced via Entra ID Connect and which are located only in the cloud is crucial for efficient management. In our previous article, we discussed the importance of having access to Entra ID Connect details, including user sync status, last successful sync, current sync agent version, server name, and service account. In this Q&A article, we will address some of the most frequently asked questions about this feature request.

Q: What is the current process for managing Entra ID Connect users?

A: Currently, MSPs have to manually log into each client's tenant or server to determine which users are synced via Entra ID Connect and which are located only in the cloud. This can be time-consuming and prone to errors.

Q: Why is it important to have access to Entra ID Connect details?

A: Having access to Entra ID Connect details would enable MSPs to better manage their clients' user accounts, improve reporting and alerting, and enhance their ability to meet compliance requirements.

Q: How would this feature benefit MSPs?

A: This feature would benefit MSPs by:

Improving the efficiency of their technicians
Enabling better reporting and alerting
Enhancing their ability to meet compliance requirements
Reducing the risk of errors and data breaches

Q: Would this feature be available for all MSPs, or only for those with a certain level of subscription?

A: This feature would be available for all MSPs with a paid subscription to Entra ID Connect.

Q: How would the feature be implemented?

A: The feature would be implemented as a column in the CIPP interface, displaying Entra ID Connect details, including user sync status, last successful sync, current sync agent version, server name, and service account.

Q: Would this feature require any additional training or support for MSPs?

A: No, this feature would not require any additional training or support for MSPs. The interface would be intuitive and easy to use.

Q: Can you provide an example of how this feature would be used in real-world scenarios?

A: For example, if an MSP has a client with 100 users, and they want to determine which users are synced via Entra ID Connect and which are located only in the cloud, they can simply log into the CIPP interface and view the Entra ID Connect details column. This would save them time and reduce the risk of errors.

Q: What are the next steps for implementing this feature?

A: We are currently working with Microsoft to implement this feature. We anticipate that it will be available in the near future.

Q: How can MSPs provide feedback and suggestions for this feature?

A: MSPs can provide feedback and suggestions for this feature by contacting our support team or by submitting a feature request on our website.

Conclusion

In conclusion, having access to Entra ID Connect details is crucial for efficient management of multiple client configurations. This feature would benefit MSPs by improving the efficiency of their technicians, enabling better reporting and alerting, and enhancing their ability to meet compliance requirements. We believe that this feature would be highly beneficial MSPs and would like to request its implementation.