[pull] dev from KelvinTegelaar:dev#2
Open
pull[bot] wants to merge 754 commits into
Open
Conversation
fix: remove unneeded stuff
…essage-Branding_OME
Added 10x configurable fields (background colour, logo URL, introduction text, read button text, email text, privacy statement URL, disclaimer text, portal text, OTP enabled, social ID sign-in) and a helpText link to the Microsoft Purview branding documentation. Signed-off-by: Chris Dewey <142454021+chris-dewey-1991@users.noreply.github.com>
…ssigned-admin-roles-to-disable-EXO-standard
Stores the entire MDE mobileThreatDefenseConnector object (heartbeat, per-platform enable/MAM/block flags, MDE attach, iOS metadata flags) in the reporting DB instead of only partnerState. Live HTTP endpoint mirrors the same shape so cached and live responses are interchangeable. Failed Graph calls still write a partnerState=unavailable row so AllTenants reports retain the tenant.
Co-authored-by: Copilot <copilot@github.com>
…Client Co-authored-by: Copilot <copilot@github.com>
Three new standards: Invoke-CIPPStandardDisableEWS (disable Exchange Web Services org-wide), Invoke-CIPPStandardSPDisableCustomScripts (disable custom scripts on SharePoint/OneDrive), and Invoke-CIPPStandardSPDisableStoreAccess (disable SharePoint Store access).
…eRegistration The standard was writing to azureADJoin.allowedToJoin despite its name — that's the join scope, not registration. Re-point reads and writes to azureADRegistration.allowedToRegister. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Restores the azureADJoin.allowedToJoin behavior that previously lived (mislabeled) inside intuneRestrictUserDeviceRegistration. Join and registration are independent scopes, so each needs its own standard. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Separate the standards for user device join and registration in Intune. Adjust the implementation to ensure that each standard operates independently, correcting previous mislabeling Frontend PR: KelvinTegelaar/CIPP#6019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )