Skip to content

Conversation

@Bajusz15
Copy link
Contributor

@Bajusz15 Bajusz15 commented Oct 28, 2025

Currently stuck.

I managed to get this working in my PR, but only if i copied the bearer token from my browser. Otherwise I just get 401, as the permissions I assign to graph API doesn't matter for this endpoint. (https://main.iam.ad.ext.azure.com/api/Directories/LcmSettings)

We need to decide if this is a practical approach to use: https://rozemuller.com/use-internal-azure-api-in-automation/ (he user will have to authenticate in the browser, and the user needs permission to see group expiration).

This requires AADInternals. For now I'm parking it.

@Bajusz15 Bajusz15 self-assigned this Oct 28, 2025
@github-actions
Copy link
Contributor

Test Results

4 554 tests  ±0   4 550 ✅ ±0   2m 44s ⏱️ +23s
  409 suites ±0       4 💤 ±0 
   30 files   ±0       0 ❌ ±0 

Results for commit 028bad6. ± Comparison against base commit d043cf9.

@tas50 tas50 changed the title Add groupIdsToMonitorExpirations to ms365 microsoft.groupLifecyclePolicies[] ⭐ Add groupIdsToMonitorExpirations to ms365 microsoft.groupLifecyclePolicies[] Nov 4, 2025
const lcmSettingsScript = `
$ErrorActionPreference = "Stop"
$Uri = 'https://main.iam.ad.ext.azure.com/api/Directories/LcmSettings'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should never call urls via powershell

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants