You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within the concept of Clients/Channel providers there are some providers that group a set of channels behind a single "public" channel.
There are currently two examples of this inside the MSFT ecosystem.
Azure Communications Services
M365 msTeams Channel
In these cases, multiple clients are fronted by a single service,
Currently, the Activity Protocol described a single channel concept called "channel Id".
To handle the updated requirements, we would introduce a new component in entitles called "subChannelId".
This subchannel would be used to describe the subchannel being fronted
Within the concept of Clients/Channel providers there are some providers that group a set of channels behind a single "public" channel.
There are currently two examples of this inside the MSFT ecosystem.
In these cases, multiple clients are fronted by a single service,
Currently, the Activity Protocol described a single channel concept called "channel Id".
To handle the updated requirements, we would introduce a new component in entitles called "subChannelId".
This subchannel would be used to describe the subchannel being fronted
This would take the shape of:
Which would existing in the structure:
The text was updated successfully, but these errors were encountered: