René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Owners not assigned correctly in bulk member add & inconsistent response behavior","articleBody":"### Describe the bug\n\nWhen creating a Team and adding members using the Microsoft Graph SDK for Java, there are two issues:\n\n1. Bulk add does not correctly assign owner roles\nWhen using the bulk member add endpoint (/teams/{id}/members/add), users specified with the role \"owner\" are not assigned as owners.\nInstead, they are added as regular members, even though the request payload explicitly defines the owner role.\n\nThis behavior occurs without any error or exception, making it difficult to detect programmatically. As a result, affected users do not receive the required owner permissions.\n\n2. createTeam does not return the created Team\nThe SDK method used to create a Team suggests that a Team object will be returned. However, the response does not contain the created Team resource.\nInstead, the Team ID must be retrieved indirectly (e.g., via response headers or additional handling), which is not aligned with common framework expectations.\n\n### Expected behavior\n\n1. Correct role assignment in bulk add\nWhen adding members via the bulk endpoint, the roles provided in the request (e.g., \"owner\") should be correctly applied.\nUsers specified as owners must be assigned owner permissions within the Team.\n2. Ability to define members and roles during Team creation\nIt should be possible to fully define all desired members and their roles (including owners) directly during Team creation, without requiring a separate bulk add step.\n\n3. Consistent and intuitive SDK response behavior\nThe createTeam operation should either:\n\n- return the created Team entity, or\n- clearly reflect (through API design and SDK behavior) that no resource is returned.\n\nIdeally, the SDK should align with common framework standards and not imply a return value that is not actually provided.\n\n### How to reproduce\n\nCreate Team\nPOST https://graph.microsoft.com/v1.0/teams\nContent-Type: application/json\n\n{\n  \"template@odata.bind\": \"https://graph.microsoft.com/v1.0/teamsTemplates('standard')\",\n  \"displayName\": \"Test Team\",\n  \"members\": [\n    {\n      \"@odata.type\": \"#microsoft.graph.aadUserConversationMember\",\n      \"roles\": [\"owner\"],\n      \"user@odata.bind\": \"https://graph.microsoft.com/v1.0/users('john.doe@xy.com')\"\n    }\n  ]\n}\nRetrieve Team ID\nThe Team ID is extracted from the response (e.g., via response headers / response options).\nBulk add members\nPOST https://graph.microsoft.com/v1.0/teams/{team-id}/members/add\nContent-Type: application/json\n\n{\n  \"values\": [\n    {\n      \"@odata.type\": \"microsoft.graph.aadUserConversationMember\",\n      \"roles\": [],\n      \"user@odata.bind\": \"https://graph.microsoft.com/v1.0/users('some.user@xy.com')\"\n    },\n    {\n      \"@odata.type\": \"microsoft.graph.aadUserConversationMember\",\n      \"roles\": [],\n      \"user@odata.bind\": \"https://graph.microsoft.com/v1.0/users('the.user@xy.com')\"\n    },\n    {\n      \"@odata.type\": \"microsoft.graph.aadUserConversationMember\",\n      \"roles\": [],\n      \"user@odata.bind\": \"https://graph.microsoft.com/v1.0/users('john.smith@xy.com')\"\n    },\n    {\n      \"@odata.type\": \"microsoft.graph.aadUserConversationMember\",\n      \"roles\": [\"owner\"],\n      \"user@odata.bind\": \"https://graph.microsoft.com/v1.0/users('one.owner@xy.com')\"\n    },\n    {\n      \"@odata.type\": \"microsoft.graph.aadUserConversationMember\",\n      \"roles\": [\"owner\"],\n      \"user@odata.bind\": \"https://graph.microsoft.com/v1.0/users('another.owner@xy.com')\"\n    }\n  ]\n}\n\n\n### SDK Version\n\n6.62.0\n\n### Latest version known to work for scenario above?\n\n_No response_\n\n### Known Workarounds\n\n_No response_\n\n### Debug output\n\nThe log contains no errors, which is also a real problem.\n\n\n### Configuration\n\n- OS: Windows Local and a Debian on the production VM but the behavior is on both systems the same\n-Within a permission management workflow implemented in a Spring Boot 3.5.x application, Teams are programmatically created and populated in a Job with members using the Microsoft Graph SDK for Java.\n\n### Other information\n\n_No response_","author":{"url":"https://github.com/hubermaxi","@type":"Person","name":"hubermaxi"},"datePublished":"2026-03-24T14:41:10Z","url":"https://github.com/microsoftgraph/msgraph-sdk-java/issues/2562"}