[GH-ISSUE #3823] [Feature Request]: Add more Azure AD Connect info #1702

Closed
opened 2026-03-02 13:46:22 +03:00 by kerem · 1 comment
Owner

Originally created by @vincent-v-c on GitHub (Mar 19, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3823

Please confirm:

  • I have searched existing feature requests (open and closed) and found no duplicates.
  • **me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

We need to update Azure AD Connect regularly for our customers. Is it possible to add more info about the Azure AD Connect per customer.

Benefits for MSPs

Service account used, version and servername would be helpful.

Value or Importance

There is a deadline currently on the 7th of april where 2.4.18 needs to be installed. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/reference-connect-version-history

PowerShell Commands (Optional)

This URL show the information in an XML:
https://admin.microsoft.com/admin/api/DirSyncManagement/manage

Originally created by @vincent-v-c on GitHub (Mar 19, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3823 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement We need to update Azure AD Connect regularly for our customers. Is it possible to add more info about the Azure AD Connect per customer. ### Benefits for MSPs Service account used, version and servername would be helpful. ### Value or Importance There is a deadline currently on the 7th of april where 2.4.18 needs to be installed. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/reference-connect-version-history ### PowerShell Commands (Optional) This URL show the information in an XML: https://admin.microsoft.com/admin/api/DirSyncManagement/manage
kerem 2026-03-02 13:46:22 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 19, 2025):

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

<!-- gh-comment-id:2736919349 --> @github-actions[bot] commented on GitHub (Mar 19, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. _Thank you for understanding,_ **The CIPP Team**
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#1702
No description provided.