microsoftgraph / microsoftgraph/msgraph-metadata
Inconsistent acceptable values in ConditionalAccess policies where "All" is supported
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
As a user of Conditional Access either directly through the API or via the Hashicorp Terraform azuread provider it is incredibly frustrating that most attributes or conditions that support a value that means "All" possible values is Camel case e.g. "All".
This includes the Users, Applications, Locations, etc conditions (All, AllTrusted.
However, there are three that only support it in lowercase e.g. "all".
These are:
Ideally either you would extend the metadata to be consistent, or amend the API endpoints to be case-insensitive (the latter would be less likely to be a breaking change vs current operation).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the metadata definitions behind clientAppTypes, platforms, and externalTenants membership_Kind, using the linked Microsoft Graph documentation to compare their accepted values with the other Conditional Access conditions. Done means the metadata or API behavior consistently accepts or represents the intended casing, with generated outputs or validation showing no regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, terraform
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100