Microsoft PL-300 Bundle

The Excel connector understands workbook navigation items and table structures. That is a different operating condition from “must be ingested together”: “tables and should be imported into Power Query”.

JSON-oriented ingestion preserves nested objects until they are expanded into tabular columns. It serves “the analyst must expand into fields”, not “must be ingested together”.

Text/CSV import parses delimited records rather than treating each file as an Excel workbook. The present requirement is “must be ingested together”; “text with a header row and encoding requirements” is a distinct situation.

Database credentials authenticate with the source's native user and password. The present requirement is “Authenticate with an Organizational account using supported OAuth”; “a database-specific login not tied to Microsoft Entra” is a distinct situation.

Windows authentication is distinct from Basic username-and-password credentials. The boundary it addresses is “Select Windows credentials for the supported integrated SQL”, while this case concerns “Authenticate with an Organizational account using supported OAuth”.

The service refresh identity is configured separately from the authoring machine's cached credentials. This solves “PBIX still opens. Where should the owner intervene”; the stated issue is “Authenticate with an Organizational account using supported OAuth”.

Connector-managed credentials can be rotated and governed independently of report code. The deciding difference is “token in every Power Query script is prohibited” versus “Select Windows credentials for the supported integrated SQL”.

The service refresh identity is configured separately from the authoring machine's cached credentials. Its application is “PBIX still opens. Where should the owner intervene”, not the need “Select Windows credentials for the supported integrated SQL”.

Organizational OAuth uses the tenant identity rather than a local Windows password. That is a different operating condition from “Select Windows credentials for the supported integrated SQL”: “Authenticate with an Organizational account using supported OAuth”.

Organizational OAuth uses the tenant identity rather than a local Windows password. That is a different operating condition from “a database-specific login not tied to Microsoft Entra”: “Authenticate with an Organizational account using supported OAuth”.

Connector-managed credentials can be rotated and governed independently of report code. The present requirement is “a database-specific login not tied to Microsoft Entra”; “token in every Power Query script is prohibited” is a distinct situation.

The service refresh identity is configured separately from the authoring machine's cached credentials. That matters for “PBIX still opens. Where should the owner intervene” rather than the condition “a database-specific login not tied to Microsoft Entra”.

The service refresh identity is configured separately from the authoring machine's cached credentials. That matters for “PBIX still opens. Where should the owner intervene” rather than the condition “token in every Power Query script is prohibited”.

Windows authentication is distinct from Basic username-and-password credentials. The boundary it addresses is “Select Windows credentials for the supported integrated SQL”, while this case concerns “token in every Power Query script is prohibited”.

Database credentials authenticate with the source's native user and password. This solves “a database-specific login not tied to Microsoft Entra”; the stated issue is “token in every Power Query script is prohibited”.

Connector-managed credentials can be rotated and governed independently of report code. The deciding difference is “token in every Power Query script is prohibited” versus “PBIX still opens. Where should the owner intervene”.

Windows authentication is distinct from Basic username-and-password credentials. That is a different operating condition from “PBIX still opens. Where should the owner intervene”: “Select Windows credentials for the supported integrated SQL”.

Organizational OAuth uses the tenant identity rather than a local Windows password. It serves “Authenticate with an Organizational account using supported OAuth”, not “PBIX still opens. Where should the owner intervene”.

Gateway mapping depends on consistent connection configuration, not merely installation. It serves “data source name differs from the published model”, not “Server is inaccessible from Power BI's cloud service”.

Personal mode does not provide the same shared administration features as standard mode. The present requirement is “Server is inaccessible from Power BI's cloud service”; “personal-mode gateway only for an individual refresh setup” is a distinct situation.

Standard mode supports shared data sources and centralized gateway management. That matters for “centralized, shared connectivity for multiple scheduled-refresh semantic models” rather than the condition “Server is inaccessible from Power BI's cloud service”.

Gateway mapping depends on consistent connection configuration, not merely installation. This solves “data source name differs from the published model”; the stated issue is “centralized, shared connectivity for multiple scheduled-refresh semantic models”.

The gateway securely relays cloud requests to private network data sources. The deciding difference is “Server is inaccessible from Power BI's cloud service” versus “centralized, shared connectivity for multiple scheduled-refresh semantic models”.

Personal mode does not provide the same shared administration features as standard mode. Its application is “personal-mode gateway only for an individual refresh setup”, not the need “centralized, shared connectivity for multiple scheduled-refresh semantic models”.

Standard mode supports shared data sources and centralized gateway management. Its application is “centralized, shared connectivity for multiple scheduled-refresh semantic models”, not the need “personal-mode gateway only for an individual refresh setup”.

A gateway is not automatically necessary for supported reachable cloud data sources. It serves “with cloud credentials and no private network restriction”, not “personal-mode gateway only for an individual refresh setup”.

Gateway mapping depends on consistent connection configuration, not merely installation. The present requirement is “personal-mode gateway only for an individual refresh setup”; “data source name differs from the published model” is a distinct situation.

Gateway mapping depends on consistent connection configuration, not merely installation. The present requirement is “with cloud credentials and no private network restriction”; “data source name differs from the published model” is a distinct situation.

Standard mode supports shared data sources and centralized gateway management. That matters for “centralized, shared connectivity for multiple scheduled-refresh semantic models” rather than the condition “with cloud credentials and no private network restriction”.

The gateway securely relays cloud requests to private network data sources. The boundary it addresses is “Server is inaccessible from Power BI's cloud service”, while this case concerns “with cloud credentials and no private network restriction”.

A gateway is not automatically necessary for supported reachable cloud data sources. This solves “with cloud credentials and no private network restriction”; the stated issue is “data source name differs from the published model”.

The gateway securely relays cloud requests to private network data sources. Its application is “Server is inaccessible from Power BI's cloud service”, not the need “data source name differs from the published model”.

Standard mode supports shared data sources and centralized gateway management. That is a different operating condition from “data source name differs from the published model”: “centralized, shared connectivity for multiple scheduled-refresh semantic models”.