starred/CIPP

Fork 0

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

[GH-ISSUE #4612] [Feature Request]: Scheduled Out Of Office #2127

New issue

Closed

opened 2026-03-02 13:49:51 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 13:49:51 +03:00

Owner

Originally created by @PTA-Wine-Step-Mom on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4612

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

Hi All,

I work for an MSP and we’re in the process of transitioning to CIPP as our all-in-one solution. One feature I’ve noticed is currently limited: while CIPP allows you to schedule Out of Office for offboarding users, the same functionality isn’t available for standard users (e.g. when someone is going on holiday or away temporarily).

It would be very useful to have the option to schedule Out of Office for active users as well. This seems like it should be relatively straightforward to implement, and I’m happy to work on it myself, but if anyone more experienced has insight into an easy way to achieve this, it would be greatly appreciated.

Thanks!

Benefits for MSPs

This significantly reduces the time and scheduling burden. Instead of technicians needing to wait until a specific time (for example, 11am) to manually set an Out of Office message, it can be scheduled in advance - days or even a week before. This streamlines workflows, improves efficiency, and ensures nothing is missed.

Value or Importance

While not a critical feature, this adds notable value to CIPP by aligning it with functionality already available in other management portals. For MSPs, it’s a “nice to have” that reduces the need for forward planning and manual oversight, allowing staff to schedule Out of Office messages in advance with minimal effort. This improves efficiency and reduces the risk of missed or delayed configurations.

PowerShell Commands (Optional)

This may or may not work this is what my supervisor and me created for now but we cannot test it yet since it is not time for him to be out of office and we dont have a test account to use. Sorry

`
param(
[Parameter(Mandatory=$true)][string]$UserPrincipalName,
[Parameter(Mandatory=$true)][datetime]$StartTime,
[Parameter(Mandatory=$true)][datetime]$EndTime,
[string]$InternalMessage = "I am currently out of the office.",
[string]$ExternalMessage = "I am currently out of the office. For urgent matters, please contact support@customer.com."
)

Connect to Exchange Online (can be scripted with stored creds or delegated auth)

Connect-ExchangeOnline -ShowProgress $false

Set Out of Office

Set-MailboxAutoReplyConfiguration -Identity $UserPrincipalName -AutoReplyState Scheduled
-StartTime $StartTime -EndTime $EndTime
-InternalMessage $InternalMessage `
-ExternalMessage $ExternalMessage

Write-Output "OOF scheduled for $UserPrincipalName from $StartTime to $EndTime"
`

Originally created by @PTA-Wine-Step-Mom on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4612 ### 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 Hi All, I work for an MSP and we’re in the process of transitioning to CIPP as our all-in-one solution. One feature I’ve noticed is currently limited: while CIPP allows you to schedule Out of Office for offboarding users, the same functionality isn’t available for standard users (e.g. when someone is going on holiday or away temporarily). It would be very useful to have the option to schedule Out of Office for active users as well. This seems like it should be relatively straightforward to implement, and I’m happy to work on it myself, but if anyone more experienced has insight into an easy way to achieve this, it would be greatly appreciated. Thanks! ### Benefits for MSPs This significantly reduces the time and scheduling burden. Instead of technicians needing to wait until a specific time (for example, 11am) to manually set an Out of Office message, it can be scheduled in advance - days or even a week before. This streamlines workflows, improves efficiency, and ensures nothing is missed. ### Value or Importance While not a critical feature, this adds notable value to CIPP by aligning it with functionality already available in other management portals. For MSPs, it’s a “nice to have” that reduces the need for forward planning and manual oversight, allowing staff to schedule Out of Office messages in advance with minimal effort. This improves efficiency and reduces the risk of missed or delayed configurations. ### PowerShell Commands (Optional) This may or may not work this is what my supervisor and me created for now but we cannot test it yet since it is not time for him to be out of office and we dont have a test account to use. Sorry ` param( [Parameter(Mandatory=$true)][string]$UserPrincipalName, [Parameter(Mandatory=$true)][datetime]$StartTime, [Parameter(Mandatory=$true)][datetime]$EndTime, [string]$InternalMessage = "I am currently out of the office.", [string]$ExternalMessage = "I am currently out of the office. For urgent matters, please contact support@customer.com." ) # Connect to Exchange Online (can be scripted with stored creds or delegated auth) Connect-ExchangeOnline -ShowProgress $false # Set Out of Office Set-MailboxAutoReplyConfiguration -Identity $UserPrincipalName ` -AutoReplyState Scheduled ` -StartTime $StartTime ` -EndTime $EndTime ` -InternalMessage $InternalMessage ` -ExternalMessage $ExternalMessage Write-Output "OOF scheduled for $UserPrincipalName from $StartTime to $EndTime" `

kerem

2026-03-02 13:49:51 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:49:52 +03:00

Author

Owner

@Zacgoose commented on GitHub (Sep 9, 2025):

This is already available under the exchange settings page for the user, you can enable, disable and schedule OOO messages.

@Zacgoose commented on GitHub (Sep 9, 2025): This is already available under the exchange settings page for the user, you can enable, disable and schedule OOO messages.

kerem commented

2026-03-02 13:49:52 +03:00

Author

Owner

@PTA-Wine-Step-Mom commented on GitHub (Sep 9, 2025):

This is already available under the exchange settings page for the user, you can enable, disable and schedule OOO messages.

Oh sorry would you mind describing where a bit better on my partner portal I cannot see an exchange settings page?

@PTA-Wine-Step-Mom commented on GitHub (Sep 9, 2025): > This is already available under the exchange settings page for the user, you can enable, disable and schedule OOO messages. Oh sorry would you mind describing where a bit better on my partner portal I cannot see an exchange settings page?

kerem commented

2026-03-02 13:49:52 +03:00

Author

Owner

@kris6673 commented on GitHub (Sep 9, 2025):

This is already available under the exchange settings page for the user, you can enable, disable and schedule OOO messages.

Oh sorry would you mind describing where a bit better on my partner portal I cannot see an exchange settings page?

Identity management -> Administration -> Users -> The 3 action dots to the right of a user -> View User. Navigate the the Exchange tab or Email and Exchange -> Administration -> Mailboxes > The 3 action dots to the right of a user -> Edit permissions :)

@kris6673 commented on GitHub (Sep 9, 2025): > > This is already available under the exchange settings page for the user, you can enable, disable and schedule OOO messages. > > Oh sorry would you mind describing where a bit better on my partner portal I cannot see an exchange settings page? Identity management -> Administration -> Users -> The 3 action dots to the right of a user -> View User. Navigate the the Exchange tab or Email and Exchange -> Administration -> Mailboxes > The 3 action dots to the right of a user -> Edit permissions :)

kerem commented

2026-03-02 13:49:52 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 9, 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

@github-actions[bot] commented on GitHub (Sep 9, 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**

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

No description provided.

Rows
Columns