Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

graphServiceClient.Teams[teamId].Delete results in HTTP 405

Open
#1,088 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 4 days

@MIchaelMainer is already working on this.

Since Apr 27, 2026.

Assessment

This issue has not been assessed yet.

Description

ToTriage
Describe the bug

I'm trying to delete a Team using

await graphServiceClient.Teams[teamId].DeleteAsync().ConfigureAwait(false);

It results in an exception that tells me the server returned HTTP 405.

Expected behavior

The Team gets deleted.

How to reproduce

Run the above code line with an existing graphServiceClient.

SDK Version

5.103

Latest version known to work for scenario above?

No response

Known Workarounds

use await graphServiceClient.Groups[teamId].DeleteAsync().ConfigureAwait(false);

Given that the REST API doc states you need to target the /groups endpoint, I think the Delete method ought to be removed from Teams so as to avoid confusion.

Debug output
Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_
Dominant language
XSLT
Stars
166
Forks
55
Avg merge
2d 11h
Merged PRs (30d)
9

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from microsoftgraph/msgraph-metadata

All issues in microsoftgraph/msgraph-metadata

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.