📄 Question
We are creating private channels using the Microsoft Graph API:
POST https://graph.microsoft.com/v1.0/teams/{team-id}/channelsWith the following payload:
{
"@odata.type": "#microsoft.graph.channel",
"displayName": "Project-Channel-001",
"description": "Sample private channel for testing",
"membershipType": "private",
"members": [
{
"@odata.type": "#microsoft.graph.aadUserConversationMember",
"user@odata.bind": "https://graph.microsoft.com/v1.0/users/{user-id}",
"roles": ["owner"]
}
]
}
🔍 Observed Behavior
When the private channel is created, the associated SharePoint site is provisioned automatically (as expected).
However, the URL format appears to have changed.
Previously observed behavior:
https://{tenant}.sharepoint.com/sites/ProjectTeamUrl-Project-Channel-001
Current behavior:
https://{tenant}.sharepoint.com/sites/ProjectTeamName-Project-Channel-001
❗ Impact
This change introduces several issues:
- Breaks deterministic URL generation logic
- Produces longer and less predictable URLs
- Introduces dependency on display name, which is mutable and may contain unexpected characters
- Impacts existing automation and integrations relying on the previous pattern
❓ Questions
- Has there been a recent change in how SharePoint site URLs are generated for private channels?
- Is this behavior intentional and documented, or a regression?
- Is there any way (via Graph or otherwise) to:
- Control the generated SharePoint site URL, or
- Retrieve the final site URL deterministically without relying on pattern assumptions?
- Is the previous
{ParentTeamUrl}-{ChannelName} format still expected in some scenarios, or has it been deprecated?
🧪 Additional Notes
- This behavior is observed when creating channels via Microsoft Graph (v1.0)
- The issue is reproducible across multiple test scenarios
🙏 Any clarification from Microsoft or others encountering this would be appreciated.
📄 Question
We are creating private channels using the Microsoft Graph API:
With the following payload:
{ "@odata.type": "#microsoft.graph.channel", "displayName": "Project-Channel-001", "description": "Sample private channel for testing", "membershipType": "private", "members": [ { "@odata.type": "#microsoft.graph.aadUserConversationMember", "user@odata.bind": "https://graph.microsoft.com/v1.0/users/{user-id}", "roles": ["owner"] } ] }🔍 Observed Behavior
When the private channel is created, the associated SharePoint site is provisioned automatically (as expected).
However, the URL format appears to have changed.
Previously observed behavior:
Current behavior:
❗ Impact
This change introduces several issues:
❓ Questions
{ParentTeamUrl}-{ChannelName}format still expected in some scenarios, or has it been deprecated?🧪 Additional Notes
🙏 Any clarification from Microsoft or others encountering this would be appreciated.