Share via

Power BI App entity not appearing in Workspace “Related” section in Microsoft Purview

Noelia Sotelo Taboada 40 Reputation points
2026-02-11T09:01:14.7033333+00:00

Hello,

I am testing the creation of a custom Power BI App entity in Microsoft Purview using the Atlas REST API and I am seeing an behavior that I would like to confirm is expected.

Scenario

I manually created a custom entity type for a Power BI App and then created an instance of that app and its relationships using the Purview Atlas API.

Steps performed

  1. Custom entity type creation I created a custom entity type (powerbi_app_ednon) derived from powerbi_resource.
  2. App entity creation I created a Power BI App entity using: POST /atlas/v2/entity/bulk With attributes including:
    • qualifiedName (powerbi-app://…)
    • appId
    • workspaceId
    • webUrl
    • name
    The app entity is successfully created and visible in the Purview catalog.
  3. Workspace → App relationship I created a relationship between the Fabric workspace and the app: POST /atlas/v2/relationship typeName: fabric_workspace_powerbi_app_ednon The workspace correctly shows the app under Related resources.
  4. App → Report relationship I created another relationship: POST /atlas/v2/relationship typeName: powerbi_app_ednon_reports linking the app to an existing Power BI report.

Issue observed

When I open the App entity in Purview, I can see:

  • The related report
  • The related workspace

However, when I open the Workspace and go to the Related tab (the section highlighted in green in the attached screenshots), I only see the report. The app does not appear in that same list where I would expect it to be shown.

All relationships return HTTP 200 and are visible via the API, so they appear to be created correctly.

Question

Is it expected behavior that a custom Power BI App entity linked to a workspace via a custom relationship does not appear in the Workspace’s Related section in the UI?

Or is there an additional requirement (entity category, relationship configuration, UI support limitation, etc.) needed for the app to appear there?

Attachments

I have attached screenshots showing:

  • The app entity view
  • The workspace entity view
  • The Related section where the app is missing
  • The API requests used to create the entity and relationships

Thank you for your help in clarifying whether this is expected behavior or a configuration issue.

Best regards,

Noelia

User's image

User's image

User's image

User's image

Query:

{
  "entityDefs": [
    {
      "category": "ENTITY",
      "name": "powerbi_app_ednon",
      "description": "Power BI App (contenida en un workspace; relaciones en Related; sin lineage)",
      "typeVersion": "1.0",
      "superTypes": ["powerbi_resource"],
      "attributeDefs": [
        {
          "name": "appId",
          "typeName": "string",
          "isOptional": false,
          "cardinality": "SINGLE",
          "valuesMinCount": 1,
          "valuesMaxCount": 1,
          "isUnique": false,
          "isIndexable": true
        },
        {
          "name": "workspaceId",
          "typeName": "string",
          "isOptional": false,
          "cardinality": "SINGLE",
          "valuesMinCount": 1,
          "valuesMaxCount": 1,
          "isUnique": false,
          "isIndexable": true
        },
        {
          "name": "webUrl",
          "typeName": "string",
          "isOptional": true,
          "cardinality": "SINGLE",
          "valuesMinCount": 0,
          "valuesMaxCount": 1,
          "isUnique": false,
          "isIndexable": false
        }
      ]
    }
  ],
  "relationshipDefs": [
    {
      "category": "RELATIONSHIP",
      "name": "fabric_workspace_powerbi_app_ednon",
      "typeVersion": "1.0",
      "relationshipCategory": "COMPOSITION",
      "endDef1": {
        "type": "fabric_workspace",
        "name": "appsEdnon",
        "isContainer": true,
        "cardinality": "SET"
      },
      "endDef2": {
        "type": "powerbi_app_ednon",
        "name": "workspace",
        "isContainer": false,
        "cardinality": "SINGLE"
      }
    },
    {
      "category": "RELATIONSHIP",
      "name": "powerbi_app_ednon_reports",
      "typeVersion": "1.0",
      "relationshipCategory": "ASSOCIATION",
      "endDef1": {
        "type": "powerbi_app_ednon",
        "name": "reports",
        "cardinality": "SET"
      },
      "endDef2": {
        "type": "powerbi_report",
        "name": "appsEdnon",
        "cardinality": "SET"
      }
    }
  ]
}

User's image

User's image

User's image

Microsoft Security | Microsoft Purview
{count} votes

Answer accepted by question author
  1. SAI JAGADEESH KUDIPUDI 485 Reputation points Microsoft External Staff Moderator
    2026-02-12T10:18:11.93+00:00

    Hi Noelia Sotelo Taboada,
    Even though the custom powerbi_app_ednon entity is created successfully, the relationships return HTTP 200, and the App entity correctly shows the related Workspace and Report, Microsoft Purview does not display custom Power BI App entities inside the Workspace → Related section of the UI.

    Purview only renders Microsoft‑supported, scanner‑discovered Power BI artifacts in that area—such as Reports, Dashboards, Datasets, Dataflows, and Datamarts. Power BI Apps are not part of the supported Power BI artifact list and therefore do not appear in the Workspace “Related” tab, even when the relationships exist and are stored correctly in the Data Map.

    Your JSON model, entity type, and relationships are valid. The screenshots you shared confirm that the App entity is created correctly, the Workspace relationship exists, and the App entity view displays all expected links. The limitation is strictly in the Purview UI rendering layer, not in your configuration.

    You can still view and validate the App entity and its relationships using:
    Catalog search
    The App entity details page
    Relationship browser
    Lineage view (if applicable to your type design)

    But at this time, the Workspace “Related” section will not show custom App entities.
    You didn’t miss any setting. This behavior comes from a limitation in how Purview’s UI works today. The relationship is saved correctly in the catalog (and you can see it through the API), but it still won’t show up in the “Related” tab for built‑in assets.

    Reference Links:
    Connect to and manage a Power BI tenant in Microsoft Purview
    https://learn.microsoft.com/en-us/purview/register-scan-power-bi-tenant
    How to get lineage from Power BI into Microsoft Purview
    https://learn.microsoft.com/en-us/purview/data-map-lineage-power-bi

    Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.