Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Pages Menu
TwitterRssFacebook

Posted by on Jun 30, 2020 in Development, Microsoft Teams

Could Microsoft Teams be about to let you set different channels as the default, replacing General?

Could Microsoft Teams be about to let you set different channels as the default, replacing General?

I noticed a new addition to the Microsoft Graph API, as detailed in the Changelog for June:

Addition - beta, v1.0 - Added primaryChannel navigation property to team resource type

This new property is available in both beta and v 1.0 and there is a documentation page for it as well:

Why is this interesting? Well, today, you can’t chose the “primaryChannel”, so it’s not immediately clear why there would be an API call to get it – as it’s always going to be “General”. In fact, the description for the call even points this out.

Perhaps this property is here to prevent developers from needing to hard-code “General” into their code base. Maybe it’s to support Teams tenants that span multiple regions where the General channel will actually be titled in the local language. Or, perhaps it’s an early indication that, in the future, you will be able to change the name of the General channel – meaning that an API call like this will be needed. There is a UserVoice for “Rename General channel” with nearly 4,000 votes.

 

 

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Buy the book: Building and Developing Apps & Bots for Microsoft Teams. Now available to purchase online with free updates.

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share to Microsoft Teams