microsoftgraph / microsoftgraph/msgraph-sdk-go

Add Microsoft Graph API support to identify and manage Shared Mailboxes

Open
#939 3 comments 4 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, Microsoft Graph does not provide a way to identify Shared Mailboxes in Exchange Online.
When querying /users, the userType property only returns Member, Guest, or Federated, and does not indicate whether the account is a shared mailbox.

This creates a compliance and automation gap:

Administrators cannot programmatically verify which accounts are shared mailboxes.

Security audits (e.g., checking that sign-in is blocked for shared mailboxes) require Exchange Online PowerShell (Get-Mailbox -RecipientTypeDetails SharedMailbox), which prevents full automation via Graph

Describe the solution you'd like.

Microsoft Graph should expose Shared Mailbox details directly. This would allow admins to retrieve shared mailbox details (e.g., mailbox type, sign-in status, licensing, members) directly via Graph.

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

Start by reviewing how the Go SDK models /users and exposes the userType property, then compare that surface with the requested shared-mailbox details. The issue also references Get-Mailbox -RecipientTypeDetails SharedMailbox as the current workaround. Done would require a defined Microsoft Graph and SDK approach for identifying and managing shared mailboxes, including the requested mailbox metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.