microsoftgraph / microsoftgraph/msgraph-sdk-dotnet

Issue updating "HideFromOutlookClients" and "HideFromAddressLists" with PATCH 1.0/Groups/{groupid}

Open
#3,053 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Service issue type:bug
Dominant language
C#
Stars
789
Forks
264
Avg merge
15h 17m
Merged PRs (30d)
3

Description

Describe the bug

We have setup a PowerAutomate flow using the HTTP connector. For the last year or two this has been working solidly but recently we started getting the following response from the API request and it seems others have encountered this very recently also (see: https://learn.microsoft.com/en-gb/answers/questions/5696935/graph-api-bug-for-teams-creation-when-try-to-set-o?page=1&orderby=Helpful&translated=false#answers):
{
"error": {
"code": "ErrorInternalServerError",
"message": "An internal server error occurred. The operation failed., Value cannot be null. (Parameter 'tenant')",
"innerError": {
"date": "2026-01-12T13:18:07",
"request-id": "3ade4b7d-5094-4d08-adb5-af43882fccfd",
"client-request-id": "3ade4b7d-5094-4d08-adb5-af43882fccfd"
}
}
}

Expected behavior

The group is hidden from the GAL and is not discoverable from Outlook Clients

How to reproduce

PATCH 1.0/groups/{groupid}

Headers:
Authorisation Bearer {token}

Body:
{
"hideFromOutlookClients": true,
"hideFromAddressLists": true
}

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

N/A

Debug output
Click to expand log ```

{
"error": {
"code": "ErrorInternalServerError",
"message": "An internal server error occurred. The operation failed., Value cannot be null. (Parameter 'tenant')",
"innerError": {
"date": "2026-01-12T13:18:07",
"request-id": "3ade4b7d-5094-4d08-adb5-af43882fccfd",
"client-request-id": "3ade4b7d-5094-4d08-adb5-af43882fccfd"
}
}
}

</details>


### Configuration

_No response_

### Other information

_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 or test is named in the report. Start by reproducing PATCH 1.0/groups/{groupid} with the supplied headers and body, then compare the internal-server-error response with the expected hidden Outlook and address-list behavior; done requires a confirmed resolution or a documented service-side cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.