Skip to content

[pull] dev from KelvinTegelaar:dev#102

Open
pull[bot] wants to merge 250 commits into
isgq-github01:devfrom
KelvinTegelaar:dev
Open

[pull] dev from KelvinTegelaar:dev#102
pull[bot] wants to merge 250 commits into
isgq-github01:devfrom
KelvinTegelaar:dev

Conversation

@pull

@pull pull Bot commented May 15, 2026

Copy link
Copy Markdown

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 : )

@pull pull Bot locked and limited conversation to collaborators May 15, 2026
@pull pull Bot added the ⤵️ pull label May 15, 2026
kris6673 and others added 24 commits May 15, 2026 20:29
…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
Zacgoose and others added 30 commits June 11, 2026 00:48
Fix SharePoint quota calculation for Multi-Geo tenants
The SecureScoreRemediation standard compared the desired state against a
non-existent top-level state property on secureScoreControlProfile, so
every configured control was PATCHed on every run, polluting the
tenant's Secure Score history in the Defender portal.
improve performance and accuracy of applied templates
…2087)

Ensure that only Secure Score controls not in the desired state are
updated, preventing unnecessary changes and preserving the integrity of
the tenant's Secure Score history. This change addresses the issue of
every configured control being PATCHed on each run due to a missing
top-level state property.
The SharePoint admin _api/StorageQuotas() endpoint returns one row per
geo location for Multi-Geo tenants instead of a single row. This broke
the two functions that consume it:

- `Get-CIPPAlertSharepointQuota` threw `[System.Object[]] does not
contain a method named 'op_Division'` because it divided
GeoUsedStorageMB by TenantStorageMB when both were arrays, so the quota
alert errored for any Multi-Geo tenant.
- `Invoke-ListSharepointQuota` used `Sort-Object GeoUsedStorageMB
-Descending | Select-Object -First 1`, reporting only the largest geo
and undercounting total usage.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants