Posts

Inside Dataverse Logs: How Microsoft Dataverse Tracks Activity and Ensures Reliability

Image
In Dataverse, logs capture system, application, and user activities that are essential for both technical operations and business governance. Technically, logs record details such as data changes (audit logs), background processes like workflows and Power Automate runs (system jobs), plugin execution traces, and integration/API calls, which help developers and administrators troubleshoot issues, analyze performance, and ensure system stability. From a business perspective, logs support compliance, security, and accountability by providing an audit trail of who did what and when, which is critical for regulated industries. Logically, they act as the platform’s “memory,” enabling visibility into system behavior, supporting root-cause analysis, and helping organizations make informed decisions about capacity planning, optimization, and risk management. What is a Log in Dataverse? In Dataverse, a log is a system record that captures what happens inside the platform when users or automate...

Dataverse Capacity Planning: Estimation Techniques Every Architect Should Know

Image
The Dataverse Capacity Estimation Model is used to predict how much storage an organization will need as data grows over time. It helps estimate database, file, and log capacity based on factors such as record volumes, data growth, retention periods, and system activities like auditing and automation. This model is important because Dataverse storage is shared and license-based, and running out of capacity can impact business operations. By using a capacity estimation model early in the design phase, organizations can plan storage accurately, control costs, avoid unexpected capacity issues, and ensure that applications remain performant and scalable as usage increases.  Step 1: Identify Data Domains Break data into categories: Step 2: Estimate Record Volume Step 3: Estimate Average Record Size Add 20–30% overhead for indexes & metadata. Step 4: Database Capacity Formula DB Capacity (GB) = (Records × Avg Size × Retention Years) × 1.3 Example (Cases): 1,000,000 × 10 KB × 2 yrs ×...

Dataverse Storage Capacity Model

Image
The Dataverse Storage Capacity Model defines how business data, documents, and system logs are stored and managed within the Power Platform. It is important because Dataverse storage is license-based and shared across the organization, so uncontrolled growth can impact both cost and system performance. By clearly separating data into database, file, and log storage, the model helps organizations store only active, high-value business data in Dataverse while moving documents and historical information to more cost-effective locations. This approach keeps applications fast, predictable, and scalable, while avoiding unexpected capacity issues and ensuring long-term sustainability of the platform. We should consider the Dataverse Storage Capacity Model in the following scenarios, especially when designing or scaling Power Platform or Dynamics 365 solutions: When building enterprise or long-running applications If the application will store large volumes of business data (such as cases, tr...

Designing Secure Power Platform Solutions with Dataverse Security Roles

Image
Understanding Dataverse Security Roles is essential for anyone working with Microsoft Power Platform and Dynamics 365—whether you are a business user, system administrator, or developer. Security roles define who can see what and do what within Dataverse by controlling access to data, actions, and system capabilities. For business users, they ensure day-to-day work is simple and secure without exposing sensitive information. For administrators, security roles provide a structured way to enforce organizational policies, compliance, and separation of duties. For developers, they are critical to designing solutions, plugins, and integrations that respect data boundaries and avoid unintended access. A well-designed security role model balances usability, performance, and compliance, ensuring the right people have the right access at the right time—no more, no less. Dataverse security is not about restriction — it’s about trust, clarity, and control. Dataverse security roles control who ca...

Solution Checker: Bridging the Gap Between Low-Code and Pro-Code Quality

Image
Solution Checker is a built-in quality assurance and analysis tool in Microsoft Power Platform that helps evaluate Dataverse solutions against Microsoft’s recommended best practices. It scans solution components such as plugins, JavaScript, Power Automate flows, apps, tables, and security roles to identify potential issues related to performance, security, reliability, and maintainability. By using rule-based and static code analysis , Solution Checker highlights risks early in the development lifecycle, helping teams fix problems before deployment. It is widely used by developers, architects, and release teams to improve code quality, reduce technical debt, prevent production issues, and ensure solutions are scalable, secure, and upgrade-ready across environments. Rule-based analysis checks “what rules you broke”, while static code analysis checks “what could go wrong in your code without running it”. What is Solution Checker? Solution Checker is a built-in quality and health check...

Managing Parallel Development and Hotfixes in Dataverse Like a Pro

Image
Managing parallel development and hotfixes in Dataverse means keeping new features and urgent fixe s moving forward at the same time without breaking the system. Because multiple teams often work in different solution layers , it becomes important to separate work clearly using branching, small modular solutions, and structured environments. While feature teams work on future releases in their own branches, hotfixes must be created quickly from the production branch, packaged in focused solutions, tested, and deployed with minimal impact. After a hotfix goes live, it must always be merged back into the development stream so it isn’t overwritten in the next release. With a good CI/CD pipeline, versioning, and clear release governance, organizations can deliver changes safely, avoid solution conflicts, and maintain stability even when several teams are building and fixing at the same time. Working with Dataverse often means several developers, consultants, and teams are customizing the...

When Things Go Wrong: The Curious Truth of Murphy's Law

Image
On Friday, we decided to shift to a new location because our current home is too far from the office. Traveling every day was taking a lot of time, and it became difficult to manage. After realizing this was our main problem, we finally chose to move out. We planned everything carefully and hired a company to help us shift our household items. Everything was going smoothly until around 11 AM, when lift maintenance work suddenly started. Even though we had informed the building team two days earlier, they were not supportive, which created unnecessary problems for us. After waiting for almost three hours, the service lift became available, and we were finally able to load our items into the truck. Later, due to city traffic restrictions, a “No Entry” zone started at 5 PM, causing further delays. When we reached our new home, the unpacking team did not work properly, and the entire house became extremely messy. It felt like problems were coming one after another, and it was difficult to ...

One Azure, Many Logins: How Users Access Microsoft’s Cloud Safely

Image
Users can access Microsoft Azure through several flexible and secure methods, depending on their role, device, and workload needs. The most common entry point is the Azure Portal, a web-based interface where users manage resources visually. For on-the-go access, the Azure Mobile App provides monitoring and basic management capabilities. Developers and administrators often prefer command-line tools such as the Azure CLI and Azure PowerShell, or the browser-based Azure Cloud Shell, which comes preconfigured with all Azure tools. For application development and automation, users access Azure through SDKs, APIs, and Visual Studio integration. Regardless of the method used, authentication and authorization are enforced through Azure Active Directory (Azure AD), ensuring secure sign-in and controlled access to resources. Microsoft Azure provides multiple ways for users to access its cloud services. These access methods depend on the user’s role, the device they use, and the type of work they...