Repository navigation
Get-MgTeamChannel [Shared Channel is reported back as unknownFutureValue] #3621
Description
Describe the bug
Description
Get-MgTeamChannel returns MembershipType = unknownFutureValue for shared channels.
According to documentation, MembershipType should return:
- standard
- private
- shared
However, shared channels are returned as "unknownFutureValue".
Steps to reproduce
-
Run:
Get-MgTeamChannel -TeamId -All | Select DisplayName, MembershipType -
Observe that shared channels are listed as:
unknownFutureValue
Actual behavior
Shared channels return:
MembershipType = unknownFutureValue
Environment
- Module version: Microsoft.Graph 2.37.0
- Module: Microsoft.Graph.Teams
- PowerShell version: 2.37.0
- OS: Mac
Expected behavior
Expected behavior
Shared channels should return:
MembershipType = shared
How to reproduce
Run towards a Team with a shared channel
Get-MgTeamChannel -TeamId -All | Select DisplayName, MembershipType
SDK Version
2.37.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
$PSVersionTable
Name Value
---- -----
PSVersion 7.6.2
PSEdition Core
GitCommitId 7.6.2
OS macOS 26.5.0
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.4
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
### Other information
_No response_
Activity
[-]Get-MgTeamChannel -TeamId $TeamsID -Filter "membershipType eq 'shared'" | select *[/-][+]Get-MgTeamChannel [Shared Channel is reported back as unknownFutureValue][/+]ramsessanchez commentedon May 27, 2026
Hello JohanssonMarkus , could you run the same command with the
-Debugflag and provide the response.JohanssonMarkus commentedon May 28, 2026
Ramses Sanchez-Hernandez (@ramsessanchez) No difference
MembershipType
unknownFutureValue
unknownFutureValue
standard
standard
standard
standard
standard
standard
standard
standard
private
private
private
private
private
private
private
gavinbarron commentedon Jun 1, 2026
JohanssonMarkus that's not the
-Debugoutput. We need to see the raw request/response shapes to help you here.JohanssonMarkus commentedon Jun 2, 2026
Gavin Barron (@gavinbarron) ok what portion of the debug you need. There is much tenant information in there which I can't share publicly
For private channels I'm getting
"membershipType": "private",
"layoutType": null,
"isArchived": false
För Shared channel
"membershipType": "unknownFutureValue",
"layoutType": null,
"isArchived": false
You can't reproduce at your end?
ramsessanchez commentedon Jun 2, 2026
JohanssonMarkus provide the debug output with the tenant information redacted. What is of interest is the request information that is included in the debug output. This will allow us to verify if the request /response is successful. From the looks of it, you are receiving a response, no request failure, and a the issue is with the contents of the response. This indicates a likely API service issue which we would not have control over. Without the debug output we cannot rule this out or perform a more thorough investigation. Furthermore, we will not reproduce on our end unless it is obvious an sdk issue which requires further investigation, at the moment we do not believe that is the case, hence why we would like to rule out the other possible issues first.
gavinbarron commentedon Jun 2, 2026
the shape and content of the request and response. That coupled with the requestId + timestamp allows us to refer the work to the team that owns the specific workload
Thanks for that fragment, that helps us look into this a bit deeper.
While we could, it's not a good use of our time., we'd need to set up test data to match your specific scenario, we have limited people to work on this stuff, so we need to be smarter about where we spend effort
JohanssonMarkus commentedon Jun 4, 2026
Gavin Barron (@gavinbarron) I agree this is a API issue I get the request back fine but with a faulty value. Who is resp. for the API request itself and who can fix this?
ramsessanchez commentedon Jun 5, 2026
JohanssonMarkus We can raise an issue with the appropriate api workload team, however, we'll need the debug info mentioned by Gavin. That way we can set that as the starting point for their investigation.
microsoft-github-policy-service commentedon Jun 9, 2026
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.