microsoftgraph / microsoftgraph/msgraph-sdk-go

Add Graph API support for Exchange Admin Center settings

Open
#937 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status:waiting-for-triage type:feature
Dominant language
Go
Stars
335
Forks
43
Avg merge
15h 19m
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe the problem.

Currently, many important Exchange Admin Center (EAC) settings (such as organization configuration, transport rules, mailbox settings, and audit policies) are only accessible via Exchange Online PowerShell. These configurations are not available through Microsoft Graph API (GA or Beta).

This creates a gap for organizations that want to automate compliance checks, monitoring, and reporting in a scalable way without relying on PowerShell. It also limits integration with modern automation platforms and SDKs that depend on REST APIs.

Describe the solution you'd like.

Microsoft Graph should provide API endpoints to retrieve and manage Exchange Admin Center (EAC) settings, similar to how other Microsoft 365 services are already exposed.

Examples of useful additions include:

  • Organization-level settings (equivalent to Get-OrganizationConfig)
  • Audit configuration (e.g., AuditDisabled, AuditBypassEnabled)
  • Mail flow / transport rules (equivalent to Get-TransportRule)
  • Mailbox policies and settings (e.g., litigation hold, mailbox audit settings)
Additional context?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is identified. Start by checking how this Go SDK exposes existing Microsoft Graph service areas and whether Exchange settings are available in the upstream API. Done would require a defined API scope and corresponding SDK support for the requested settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, powershell
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.