starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #4122] [Feature Request]: Add "Office Location" Block to user creation. #1870

New issue

Closed

opened 2026-03-02 13:47:46 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:47:46 +03:00

Owner

Originally created by @DKENT-SysAdmin on GitHub (May 21, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4122

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

Hello,

I recently implemented CIPP to streamline M365 management across my MSP's tenants. The whole point of this implementation was to have one central control for my technicians to manage s65 functions, but I have run into an issue. The "Office Location" block isn't available to input data when creating a new user like it is within the 365-admin center and Entra. This is a big deal for my MSP because 365 configurations are directly synced into our PSA, which is how billing is for our tenants. This becomes an issue when our clients have multiple locations and users are being created with no office location, it directly affects billing when handling tickets and user organization within our knowledge base. This seems like a small yet powerful change that should be implemented within CIPP because as of right now, our technicians still have to create users within the 365-admin center just so they can input the office location that CIPP currently does not obtain.

Benefits for MSPs

this will reduce time by being able to configure this on the CIPP platform instead of having technicians log into a client's admin center every time they need to create a new user. This will in fact offer clarity within documentation and streamline an MSP wide commonly repeated task.

Value or Importance

Without this feature, technicians will get confused on which location a user is located due to a ticket being created not having the proper information. This directly affects billing when a ticket is completed, Troubleshooting / SLA times of our tickets, and information that is synced with our knowledge base IT glue.

PowerShell Commands (Optional)

No response

Originally created by @DKENT-SysAdmin on GitHub (May 21, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4122 ### 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 Hello, I recently implemented CIPP to streamline M365 management across my MSP's tenants. The whole point of this implementation was to have one central control for my technicians to manage s65 functions, but I have run into an issue. The "Office Location" block isn't available to input data when creating a new user like it is within the 365-admin center and Entra. This is a big deal for my MSP because 365 configurations are directly synced into our PSA, which is how billing is for our tenants. This becomes an issue when our clients have multiple locations and users are being created with no office location, it directly affects billing when handling tickets and user organization within our knowledge base. This seems like a small yet powerful change that should be implemented within CIPP because as of right now, our technicians still have to create users within the 365-admin center just so they can input the office location that CIPP currently does not obtain. ### Benefits for MSPs this will reduce time by being able to configure this on the CIPP platform instead of having technicians log into a client's admin center every time they need to create a new user. This will in fact offer clarity within documentation and streamline an MSP wide commonly repeated task. ### Value or Importance Without this feature, technicians will get confused on which location a user is located due to a ticket being created not having the proper information. This directly affects billing when a ticket is completed, Troubleshooting / SLA times of our tickets, and information that is synced with our knowledge base IT glue. ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:47:46 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:47:47 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (May 21, 2025):

!support

@KelvinTegelaar commented on GitHub (May 21, 2025): !support

kerem commented

2026-03-02 13:47:47 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 21, 2025):

Hello,

Thank you for reaching out! This report has been classified as a support request rather than a bug or feature request. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support.

Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions—many questions have been answered there.

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

Thank you for your understanding,
The CIPP Team

@github-actions[bot] commented on GitHub (May 21, 2025): Hello, Thank you for reaching out! This report has been classified as a **support request** rather than a bug or feature request. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support. Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions—many questions have been answered there. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment, and we’ll gladly reopen the request. _Thank you for your understanding,_ **The CIPP Team**

kerem referenced this issue

2026-03-02 13:58:26 +03:00

[PR #1870] [MERGED] Various frontend changes #3460

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#1870

No description provided.

Rows
Columns