Endpoints like /groups/{group-id}/team/channels/{channel-id}/messages and all its nested resources, like /groups/{group-id}/team/channels/{channel-id}/messages/{message-id} or /groups/{group-id}/team/channels/{channel-id}/messages/{message-id}/hostedContents and so forth doesn't seem to be supported.
Even though they are being generated in the OpenAPI description:
Calling the API directly from teams/{teams-id}/channels/{channel-id}/messages (not groups) and other nested resources works just fine.
Because of that, we are also generating cmdlets for non-supported paths in our PowerShell module:
The only non-supported path under /teams/... I've noticed is teams/{teams-id}/channels/{channel-id}/messages/$count.
Endpoints like
/groups/{group-id}/team/channels/{channel-id}/messagesand all its nested resources, like/groups/{group-id}/team/channels/{channel-id}/messages/{message-id}or/groups/{group-id}/team/channels/{channel-id}/messages/{message-id}/hostedContentsand so forth doesn't seem to be supported.Even though they are being generated in the OpenAPI description:
Calling the API directly from
teams/{teams-id}/channels/{channel-id}/messages(not groups) and other nested resources works just fine.Because of that, we are also generating cmdlets for non-supported paths in our PowerShell module:
The only non-supported path under
/teams/...I've noticed isteams/{teams-id}/channels/{channel-id}/messages/$count.