Skip to content

[pull] master from KelvinTegelaar:master#143

Merged
pull[bot] merged 67 commits into
itlogic-github:masterfrom
KelvinTegelaar:master
Jun 18, 2026
Merged

[pull] master from KelvinTegelaar:master#143
pull[bot] merged 67 commits into
itlogic-github:masterfrom
KelvinTegelaar:master

Conversation

@pull

@pull pull Bot commented Jun 18, 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 : )

kris6673 and others added 30 commits June 4, 2026 17:44
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.
…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.
@pull pull Bot locked and limited conversation to collaborators Jun 18, 2026
@pull pull Bot added the ⤵️ pull label Jun 18, 2026
@pull pull Bot merged commit 19d6dda into itlogic-github:master Jun 18, 2026
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.

5 participants