[GH-ISSUE #2382] [Feature Request]: Standard: Set Office Release Preference #1213

Closed
opened 2026-03-02 13:42:26 +03:00 by kerem · 4 comments
Owner

Originally created by @bpbmcs on GitHub (Apr 30, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2382

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

Ability to set the office release channel such as to targeted or not would be great to add into the standards list. We typically always update to targeted and would be one less thing to have to manage separately.

This would benefit everyone just by being able to manage centrally in the standards section.

https://learn.microsoft.com/en-us/microsoft-365/admin/manage/release-options-in-office-365?view=o365-worldwide&redirectSourcePath=%252fen-us%252farticle%252fSet-up-the-Standard-or-Targeted-release-options-in-Office-365-3B3ADFA4-1777-4FF0-B606-FB8732101F47

PowerShell commands you would normally use to achieve above request

No response

Originally created by @bpbmcs on GitHub (Apr 30, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2382 ### Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole. Ability to set the office release channel such as to targeted or not would be great to add into the standards list. We typically always update to targeted and would be one less thing to have to manage separately. This would benefit everyone just by being able to manage centrally in the standards section. https://learn.microsoft.com/en-us/microsoft-365/admin/manage/release-options-in-office-365?view=o365-worldwide&redirectSourcePath=%252fen-us%252farticle%252fSet-up-the-Standard-or-Targeted-release-options-in-Office-365-3B3ADFA4-1777-4FF0-B606-FB8732101F47 ### PowerShell commands you would normally use to achieve above request _No response_
kerem 2026-03-02 13:42:26 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (May 2, 2024):

Great! I assigned you (@kris6673) to the issue. Have fun working on it!

<!-- gh-comment-id:2091028115 --> @github-actions[bot] commented on GitHub (May 2, 2024): Great! I assigned you (@kris6673) to the issue. Have fun working on it!
Author
Owner

@github-actions[bot] commented on GitHub (May 2, 2024):

Great! I assigned you (@kris6673) to the issue. Have fun working on it!

<!-- gh-comment-id:2091028419 --> @github-actions[bot] commented on GitHub (May 2, 2024): Great! I assigned you (@kris6673) to the issue. Have fun working on it!
Author
Owner

@kris6673 commented on GitHub (May 2, 2024):

Whoops, wrong FR. I tried working on it a few months ago but could not figure it out :(

<!-- gh-comment-id:2091032797 --> @kris6673 commented on GitHub (May 2, 2024): Whoops, wrong FR. I tried working on it a few months ago but could not figure it out :(
Author
Owner

@KelvinTegelaar commented on GitHub (May 7, 2024):

No API access to this, and MS is moving everyone over to monthly anyway in the next couple of months so seems like a moot point. :)

<!-- gh-comment-id:2097665777 --> @KelvinTegelaar commented on GitHub (May 7, 2024): No API access to this, and MS is moving everyone over to monthly anyway in the next couple of months so seems like a moot point. :)
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#1213
No description provided.