You're reading from Digital Transformation with Dataverse for Teams Become a citizen developer and lead the digital transformation wave with Microsoft Teams and Power Platform

Product type Paperback

Published in Oct 2021

Publisher Packt

ISBN-13 9781800566484

Length 298 pages

Edition 1st Edition

Tools

Microsoft Teams

Concepts

Business Management

Author (1):

Srikumar Nair

View More author details

Table of Contents (17) Chapters

Preface

1. Section 1: Introduction to Microsoft Dataverse for Teams

2. Chapter 1: Introducing Digital Transformation and the Role of Low-Code/No-Code Platform FREE CHAPTER

3. Chapter 2: Exploring Microsoft Dataverse for Teams

4. Chapter 3: Building Your First App with Microsoft Dataverse for Teams

5. Chapter 4: Enhancing Your App with Images, Screens, and File Attachments

6. Section 2: Deep Dive into Microsoft Dataverse for Teams

7. Chapter 5: Understanding Microsoft Dataverse

8. Chapter 6: Automating with Microsoft Dataverse for Teams

9. Chapter 7: Building Power Virtual Agents Bots with Microsoft Dataverse for Teams

10. Section 3: Application and Environment Life Cycle Management

11. Chapter 8: Managing the Application Life Cycle and Environment Life Cycle

12. Chapter 9: Upgrading to Microsoft Dataverse Environment

13. Section 4: Enterprise Readiness and Licensing

14. Chapter 10: Ensuring Enterprise Readiness: Security and Governance

15. Chapter 11: Licensing for Microsoft Dataverse and Dataverse for Teams

16. Other Books You May Enjoy

Packt is searching for authors like you

Reasons for Upgrading to Microsoft Dataverse

In this section, we will be looking at the scenarios for which an upgrade to a standard Dataverse environment might be needed. There are three reasons why you would consider upgrading a Dataverse for Teams environment into a standard Dataverse environment. These are Capacity, Capabilities, and Control. Let's look at each of these categories and their corresponding details.

Capacity

There are some capacity restrictions while using Dataverse for Teams environments. These restrictions are mainly around the following parameters:

Number of environments that you are allowed to create within a tenant
Amount of storage allowed per environment and per tenant (sum of all storage across all environments)
Number of API requests that a user can make within a 24-hour duration

There are pre-defined values for each of the preceding limits based on the Office family of licenses, and Microsoft has defined them here:

...