Power BI Template Apps - Installing, Sharing and Updating Without the Headaches

Template apps are one of those Power BI features that look trivially easy in a demo and then catch people out about three weeks later. Somebody in finance installs the Xero or Salesforce app from AppSource, connects it, shares it with the team, and everyone's happy. Then the publisher pushes an update, someone clicks "Update the workspace and the app", and the custom page the finance lead spent a weekend building is gone.

I've seen that exact sequence play out at two Australian clients this year. Neither was a disaster, but both were avoidable. So this post covers the full lifecycle of a template app from the consumer side: installing it, connecting it to your data, sharing it with the people who need it, and dealing with updates in a way that doesn't wipe your work.

Microsoft's own documentation on this is Install, share, and update template apps in your organisation, and it's worth reading alongside this. What follows is the consulting-floor version.

What a template app actually gives you

A template app is a packaged bundle of a semantic model, reports and a dashboard, published by Microsoft or a third party through AppSource. When you install one, Power BI creates a new workspace in your tenant and drops all that content into it. You then point the semantic model at your own data source, and the reports light up with your numbers instead of the sample data.

That's the appeal. You skip the modelling work for a well-known system and get something usable in an afternoon. For common SaaS platforms like Zendesk, Dynamics 365, GitHub or Google Analytics, a template app is often a perfectly decent starting point.

The catch is that you're inheriting someone else's opinion about what matters. The publisher picked the measures, the relationships and the visuals. Sometimes those choices are excellent. Sometimes they reflect a US sales team's view of the world that doesn't map to how an Australian distribution business tracks margin. Go in knowing you'll probably end up customising, and plan for that from day one.

Installing a template app

The install itself is simple. From the Power BI service you go to Apps, choose Get apps, pick the Template apps tab and find the one you want. You can also install directly from AppSource.

A few things trip people up here:

Tenant settings. Your Power BI admin controls whether template apps can be installed at all, and whether apps not listed in AppSource can be installed. If the Get apps button doesn't show template apps or the install fails silently, check with your admin before you start troubleshooting anything else. In larger organisations this is often locked down, and honestly, it probably should be. Template apps can connect to external services with stored credentials, so someone ought to be thinking about that.

Licensing. Installing creates a workspace, which means you need a Power BI Pro or Premium Per User licence, or the workspace needs to sit on Premium or Fabric capacity. Free users can't install template apps. That sounds obvious but I've had more than one call where the actual problem was a user without a Pro licence trying to install something from AppSource.

Workspace naming. The installer creates a workspace named after the app. If you install the same app twice (for example, once for testing and once for production) you'll get two workspaces with similar names. Rename them straight away to something meaningful. "Zendesk - Prod" and "Zendesk - Sandbox" save a lot of confusion later.

Connecting to your data

Once installed, the app opens with sample data and a banner prompting you to connect your data. This is where you enter the parameters the publisher defined, typically a URL, tenant ID or account name, then authenticate.

Some practical notes from doing this a lot:

• Use a service account where you can. If you authenticate with your own personal credentials, the scheduled refresh runs under your identity. When you leave the company or your password changes, refresh breaks. For any app that's going to be used by more than one person, set it up with a dedicated account that has read-only access to the source system.
• Check the refresh schedule. After connecting, Power BI usually sets up a default scheduled refresh. Go into the semantic model settings and confirm the schedule and time zone. The default time zone is UTC unless you change it, which means your "daily 6am refresh" might actually run at 4pm or 5pm Sydney time depending on daylight saving. That one comes up constantly.
• Watch the first refresh. Big source systems can take a long time on the first full load, and some publisher models aren't built with incremental refresh. If the first refresh times out, that tells you something about whether this app will scale for your data volume.

Sharing the app with your organisation

Here's where template apps differ from ordinary workspace content in a way people don't always grasp. Installing the template app gives you a workspace. To get it to other users, you then publish an org app from that workspace, just like any other Power BI app.

So the flow is: install, connect, customise if needed, then publish the app to your organisation with whatever audience settings you want. You can share it with the whole organisation, specific security groups, or individual people. With the newer org app experience you can also set up multiple audiences, so the sales team sees one set of reports and leadership sees another.

My recommendations:

1. Share to security groups, not individuals. Every time. Individual sharing becomes unmanageable within months, and nobody remembers who has access when someone changes roles.
2. Keep workspace access tight. Workspace members can edit content. App audiences can only view. Most people only need to view, so they should get the app, not workspace access.
3. Decide who owns it. Template apps have a habit of becoming orphans. Someone installs it, shares it, then moves on. Assign a named owner who's responsible for refresh failures and updates.

If you need row-level security, be aware that template apps generally don't come with RLS configured for your organisation's structure. You'd need to add roles to the semantic model yourself, and that counts as a customisation, which brings us to the bit that bites people.

Updating a template app

When the publisher releases a new version, workspace admins see a notification in the Power BI service. You then get a choice of how to apply the update, and this choice matters a lot.

The options are broadly:

• Update the workspace and the app. This overwrites the existing content in the workspace with the new version and republishes the org app. Any changes you made to the reports, dashboard or semantic model are lost.
• Update only the workspace content without publishing the app. This overwrites the workspace content but leaves the published app alone, so you can review before pushing changes to users. Your customisations are still overwritten in the workspace.
• Install as a new app. This creates a separate workspace with the new version and leaves your existing one untouched. You can compare them side by side and decide what to bring across.

Microsoft is upfront in the docs that overwriting replaces content and that parameters and authentication are kept. But "parameters and authentication are kept" is doing a lot of work in that sentence. Your connection survives. Your custom pages, extra measures and tweaked visuals do not.

What I tell clients: if you've customised anything at all, choose "install as a new app" every time. Yes, it's more work. You'll need to reconnect the data source and republish. But you get to see what changed in the new version, and you can bring your customisations across deliberately instead of discovering they've vanished when a manager emails asking where their report went.

A better pattern for customisation

If you know you're going to customise heavily (and most organisations do), there's a cleaner approach than editing the template app's reports directly.

Install the template app and connect it. Then build your own reports in a separate workspace, connected live to the template app's semantic model. Your custom reports live outside the template app workspace, so updates to the template don't touch them. You can still use the publisher's model as the foundation.

There's a limitation: if the publisher changes measure names or removes tables in an update, your reports will break. But that's a visible, fixable break, which beats silently losing a week of report building.

For organisations further along, the honest answer is often that the template app was a good prototype and the real solution is a proper semantic model built for your business. We've done this transition with a few clients where the template app proved the value in a month, and then we built something properly governed in Fabric that pulled from the same source system plus their ERP. The template app did its job. It just wasn't meant to be the long-term home. Our Power BI consultants do this kind of work regularly, and if you're heading in that direction on Fabric, our Microsoft Fabric consultants page has more on how we approach it.

What's still rough

A few honest gripes:

• Update notifications are easy to miss. They appear in the workspace, and if nobody's looking at the workspace (because everyone uses the app), updates sit there for months.
• No changelog to speak of. Most publishers don't explain what changed between versions. You're left comparing workspaces by eye.
• Quality varies wildly. Some third-party template apps are excellent. Others clearly haven't been touched since they were published and break against newer API versions of the source system. Check the publish date and reviews before you commit.
• Deleting is clunky. Removing a template app means deleting the workspace and the app separately. Leftover workspaces with stale stored credentials are a security tidy-up job waiting to happen.

Where this fits

Template apps are a reasonable on-ramp to reporting for a SaaS system you already use, particularly for small and mid-sized organisations without a dedicated BI team. Install it, use it for a few weeks, find out what people actually look at. That's useful information in itself.

Just treat it as a starting point rather than a finished product, put an owner on it, and never click "update the workspace and the app" on something you've customised. If you're trying to work out where template apps fit in a broader reporting and analytics plan, have a look at how we approach AI for business intelligence or just get in touch.