Creating a Team always returns an empty Team : Cannot get the ID of the created Team.

Open

#2,238 opened on Nov 28, 2024 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 38/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: java
Domain: api

Research direction

Start with the teams().post(team) call in the Java SDK and compare its behavior in version 6.21.0 with the reported 5.x behavior. Inspect how the create response exposes the Team ID and operation ID, then verify that the result is no longer null and both values are accessible.

Written by the indexing model from the issue text.

Description

Needs: Attention :wave: type:question

Describe the bug

Hello,

I'm using com.microsoft.graph:microsoft-graph:6.21.0 right now.

I'm trying to create a new team and then to get the ID, and the Operation ID of the result.

Team result = getGraphClient().teams().post(team);

The returned Team is always null as the JSON returned by the API is always empty. It seems that those informations are returned in the response header but I cannot access to it as the response is just a Team object.
In v5, it was returned in the object.

How am I supposed to retrieve the ID and the Operation ID of a newly created Team ?

Expected behavior

I expected that the returned Team object will contain the ID and the Operation as it was the case in the v5 of this library.

How to reproduce

Create a team with the code :

Team result = getGraphClient().teams().post(team);

The result will always be a null object.

SDK Version

6.21.0

Latest version known to work for scenario above?

5.x

Known Workarounds

None

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_

Dominant language: Java
Stars: 444
Forks: 154
Avg merge: 18h 28m
Merged PRs (30d): 4

Contributor guide

Open the contributing guide

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.

Similar issues

Compatibility certification request for FJ-EAP 2.1.0 for Jakarta EE Platform 11 Open

certification

Difficulty 1/5 Under an hour Newbie friendliness 80/100

jakartaee/platform#1359 · Opened Sep 24, 2026
Python guide test runner copies stale Micronaut Test Resources state Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

micronaut-projects/micronaut-guides#1856 · Opened Sep 23, 2026
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Open

bug ecr

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

floci-io/floci#4264 · Opened Sep 23, 2026
Drop point numbers from GitHub milestones Open

Needs: Triage Type: Feature request

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

AntennaPod/AntennaPod#8794 · Opened Sep 23, 2026
[aw] Issue Classification Agent timed out Open

agentic-workflows

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

github/copilot-sdk#2760 · Opened Sep 23, 2026

More Java issues