Book Image

Customizing Microsoft Teams

By : Gopi Kondameda
Book Image

Customizing Microsoft Teams

By: Gopi Kondameda

Overview of this book

In the evolving remote working arrangement, the demand for custom Microsoft Teams apps is increasing rapidly across businesses. If you are someone who aims to provide users with an exceptional experience through custom-built apps that adhere to industry standards and good governance, Customizing Microsoft Teams is for you! The book starts with an overview of Microsoft Teams customization and configuration prerequisites. It then shows you how to expose functionalities from various solutions through tabs, connectors, messaging extensions, and more before you move on to explore how the PowerShell module can manage multiple aspects of administration and how to use the SharePoint Framework for creating custom Microsoft Teams apps. You’ll be able to work with Microsoft Dataverse for Teams to build custom apps, bots, and flows using Power Apps, Power Virtual Agents, and Power Automate. As you publish your production-ready apps on the Teams store and Microsoft AppSource, you’ll also understand Teams app analytics and reporting functionalities. By the end of this book, you’ll have learned how to develop custom solutions to solve critical business problems and extend the power of Microsoft Teams to develop high-value use cases in the remote working culture.
Table of Contents (16 chapters)
Part 1: Microsoft Teams Customization Exploring the Architecture and Components
Part 2: Microsoft Teams Customization with Tools and Techniques
Part 3: Microsoft Teams Customization with Low-Code and No-Code

Best practices with the Graph API

If you are using the Graph API in your scenario, you must follow some best practices so that you don’t encounter performance issues, making your applications more reliable. In this section, we will talk about a few of them.


You may have scenarios that require a Microsoft Graph API call to return multiple pages of data when you issue a query that may require pagination. This could happen either due to server-side paging or the query using the $top query parameter (client-driven pagination) to restrict the number of returned records.

You can review the following link for more details on understanding how you can manage pagination:


With batching, you can optimize queries to MS Graph by combining multiple requests into a single request. Batching reduces network latency significantly and consumes lower bandwidth.

You can review the following link for more details...