M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Solution publisher

Concept

The owner label of a Power Platform solution; it controls which components other publishers may change and defines the prefix added to the names of custom tables and columns.

✦ CONCEPTSolution publisherM365.FM
Title graphic: Solution publisher (Concept)

Description

A solution publisher is the owner label attached to a Power Platform solution. Every solution has a publisher, which is chosen when the solution is created. The publisher indicates who developed the app and acts as the owner of the components created in its solutions. It also defines the prefix that is added to the names of custom tables and columns. In Dynamics 365 and Power Platform projects, the publisher is one of the first things to settle before any customization work begins.

The publisher serves two main purposes. First, it identifies ownership. The owner decides which changes other publishers may make to the components it owns, and ownership can move within one publisher but not across publishers. Second, it supplies a prefix, such as a short company name, which is added to the names of the metadata the publisher creates. This prefix helps avoid naming collisions when solutions from different publishers are installed in the same environment. The episode "Deploy Dynamics 365 Customizations with ALM Pipelines" describes the publisher as the identity for customizations: it tells the system who created each component, which matters when solutions move between environments or when several teams work in the same system. It gives the example of a publisher prefix "abc", which the system then adds to every new component, such as a new table.

Timing matters because metadata names cannot be renamed after creation. The prefix should therefore be set before any apps or metadata are built. The same applies to the publisher itself: once a publisher is set on a component in a managed solution, it cannot be changed. A prefix chosen casually, or left at a default value, stays attached to the components that carry it.

Without a custom solution, work lands in the default system solutions, which are tied to default publisher settings. Microsoft Learn advises creating a dedicated publisher with a meaningful name instead of relying on the default. It also advises using a single publisher across solutions, so that the layering model can be changed later. Using one consistent publisher keeps ownership clear and avoids situations where components of one solution cannot be modified from another because they belong to a different publisher.

In practice, the publisher comes up in several typical situations. A team starting a new project creates the publisher first, sets a short and recognizable prefix, and then creates the solution. A team that automates deployments uses clear naming and versioning together with the publisher, so that the same identity travels from development to test and production environments. A company with several teams or partners has to decide whether to share one publisher or separate them, keeping in mind that ownership cannot be transferred across publishers and that components from different publishers can only be changed as far as their owner allows.

The publisher should not be confused with a marketplace publisher. The episode "The Hard Way to Get Listed on Microsoft Marketplace" covers a different concept: Publisher and Offer IDs that must be correct and active when an app is submitted for review, with incorrect or inactive IDs listed as a common error. That publisher account concerns marketplace listing, while the solution publisher discussed here concerns component ownership and naming inside Power Platform environments.

In short, the solution publisher is a small setting with long-lasting effects. It determines the naming prefix of custom tables and columns, records who owns each component, and governs how other publishers can change those components. Because neither the prefix nor the publisher on a managed component can be changed afterward, the recommended approach in the sources is to define one dedicated, meaningfully named publisher up front and use it consistently.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What does a solution publisher control in Power Platform? (AI)

It acts as the owner of components created in its solutions, decides which changes other publishers may make to them, and defines the prefix added to the names of custom metadata such as tables and columns.

Can the publisher prefix be changed after components are created? (AI)

No. Metadata names cannot be renamed after creation, so the prefix should be set before any apps or metadata are built. A publisher set on a component in a managed solution also cannot be changed.

Should a project use the default publisher? (AI)

Microsoft Learn advises creating a dedicated publisher with a meaningful name instead of using the default, and using a single publisher so the layering model can be changed later.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Maintained by Mirko Peters (Microsoft MVP) · Last updated: