Microsoft doubles free Dataverse storage on common Power Apps licences

Until now, many citizen builders treated Dataverse as expensive the moment a list grew or a few apps shared tables. SharePoint lists stayed the default because the included Dataverse pool felt small and add-on capacity looked like a surprise bill. That fear shaped a lot of half-finished canvas apps stuck on galleries, filters, and permission quirks that SharePoint never quite solved cleanly. The new defaults shrink that storage panic for mid-size internal apps without changing the real tradeoffs. You still need the right Premium path for production Dataverse in many cases, and you still own formulas, relationships, and environments. What changed is the headroom: moderate structured data is less likely to force an early capacity purchase, so the SharePoint-versus-Dataverse choice can rest more on data shape and reliability than on fear of running out of gigabytes next quarter.