You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5eaf4a5
Browse filesBrowse the repository at this point in the historyBrowse files
fix(credentials): decrypt Microsoft app secrets only on a token miss and scope the ADX operation
- Token cache key is named before decrypting, so a cached token skips the
decrypt and parse; Azure Data Explorer authorization no longer decrypts,
and its cluster key includes the resource's clouds.
- The ADX operation re-checks the credential against the run's workspace or
organization, as the AWS operation path does.
- A credential in the wrong Microsoft cloud is refused as cloud_mismatch with
its own message instead of "reconnect the credential"; ADX tool errors come
from the refusal code, not log detail.
- The operation-minted service comes from the shared ADX credential config.
- Reconnect reopens a national-cloud credential on its stored cloud.
- China signs in at login.partner.microsoftonline.cn (Entra national-cloud
reference) for both ADX auth paths; Kusto authorities derive from
MICROSOFT_CLOUDS.
- Drop the one-line ADX operations passthrough; refresh TSDoc and the Power BI
description.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/microsoft-app-credentials.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ Every option resolves on Sim's servers at run time, and tokens never appear in b
47
47
48
48
## National clouds [#national-clouds]
49
49
50
-
Choose the **Cloud** the app is registered in: **Global** (which includes Microsoft 365 GCC), **US Government (GCC High)**, **US Government (DoD)**, or **China (operated by 21Vianet)**. Each is a separate Microsoft Entra deployment, and tokens from one cloud don't work in another. Sim signs in at that cloud's endpoint (`login.microsoftonline.com`, `login.microsoftonline.us`, or `login.chinacloudapi.cn`) and checks the app against that cloud's Microsoft Graph when you save.
50
+
Choose the **Cloud** the app is registered in: **Global** (which includes Microsoft 365 GCC), **US Government (GCC High)**, **US Government (DoD)**, or **China (operated by 21Vianet)**. Each is a separate Microsoft Entra deployment, and tokens from one cloud don't work in another. Sim signs in at that cloud's endpoint (`login.microsoftonline.com`, `login.microsoftonline.us`, or `login.partner.microsoftonline.cn`) and checks the app against that cloud's Microsoft Graph when you save.
51
51
52
52
Only **Azure Data Explorer** runs outside the global cloud: a cluster in `kusto.usgovcloudapi.net` takes a US Government credential, and one in `kusto.chinacloudapi.cn` a China credential. The Azure AD, SharePoint, Intune, Power BI, Dataverse, and Dynamics 365 blocks call global-cloud endpoints, so they refuse a national-cloud credential, and a Dataverse environment URL can be saved only on a global credential.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/powerbi.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Sim requests these scopes when someone connects a Power BI account. For a self-h
29
29
30
30
## Use the block [#usage-instructions]
31
31
32
-
Connect a home-tenant organizational account through the Power BI Microsoft connection, or run as an app registration with a Microsoft app credential, to list named workspaces, inspect reports and semantic models, execute DAX queries, request standard refreshes, and read refresh history. Microsoft Graph connections cannot substitute for this delegated OAuth connection. An app credential needs the Power BI tenant setting that allows service principals to use Power BI APIs and its service principal added to each workspace as a Member or Admin; DAX queries do not run as a service principal against semantic models with row-level security or SSO. Self-hosted installations use the shared Microsoft app registration and register /api/auth/oauth2/callback/microsoft-powerbi as a Web redirect URI. Workspace listing supports a result limit, offset, and OData filter; reports and semantic models return flat lists. Read-only models may contain only their ID and name, and paginated reports may omit their semantic-model ID. Missing optional fields are null and do not establish permission or feature availability. Keep results small with summaries or TOPN: provider JSON reads are limited to 20 MiB, and workflow tool responses have a stricter 10 MiB inline budget. My Workspace, cross-tenant guest configuration, Credential Groups, impersonation, enhanced refresh, report exports, dashboards, and triggers are outside this version.
32
+
Connect a home-tenant organizational account through the Power BI Microsoft connection, or run as an app registration with a Microsoft app credential, to list named workspaces, inspect reports and semantic models, execute DAX queries, request standard refreshes, and read refresh history. A Microsoft Graph connection cannot substitute for the Power BI connection or app credential. An app credential needs the Power BI tenant setting that allows service principals to use Power BI APIs and its service principal added to each workspace as a Member or Admin; DAX queries do not run as a service principal against semantic models with row-level security or SSO. Self-hosted installations use the shared Microsoft app registration and register /api/auth/oauth2/callback/microsoft-powerbi as a Web redirect URI. Workspace listing supports a result limit, offset, and OData filter; reports and semantic models return flat lists. Read-only models may contain only their ID and name, and paginated reports may omit their semantic-model ID. Missing optional fields are null and do not establish permission or feature availability. Keep results small with summaries or TOPN: provider JSON reads are limited to 20 MiB, and workflow tool responses have a stricter 10 MiB inline budget. My Workspace, cross-tenant guest configuration, Credential Groups, impersonation, enhanced refresh, report exports, dashboards, and triggers are outside this version.
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/integrations/components/connect-service-account-modal/keyless-connection.tsx
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -73,6 +73,8 @@ export function useKeylessSetup<P extends WorkloadIdentityProvider>({
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/integrations/components/connect-service-account-modal/microsoft-app-account-modal.tsx
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ function MicrosoftAppAccountForm({
description: 'Query semantic models and manage reports and refreshes',
28
-
longDescription: `Connect a home-tenant organizational account through the Power BI Microsoft connection, or run as an app registration with a Microsoft app credential, to list named workspaces, inspect reports and semantic models, execute DAX queries, request standard refreshes, and read refresh history. Microsoft Graph connections cannot substitute for this delegated OAuth connection. An app credential needs the Power BI tenant setting that allows service principals to use Power BI APIs and its service principal added to each workspace as a Member or Admin; DAX queries do not run as a service principal against semantic models with row-level security or SSO. Self-hosted installations use the shared Microsoft app registration and register /api/auth/oauth2/callback/microsoft-powerbi as a Web redirect URI. Workspace listing supports a result limit, offset, and OData filter; reports and semantic models return flat lists. Read-only models may contain only their ID and name, and paginated reports may omit their semantic-model ID. Missing optional fields are null and do not establish permission or feature availability. Keep results small with summaries or TOPN: provider JSON reads are limited to 20 MiB, and workflow tool responses have a stricter 10 MiB inline budget. My Workspace, cross-tenant guest configuration, Credential Groups, impersonation, enhanced refresh, report exports, dashboards, and triggers are outside this version.`,
28
+
longDescription: `Connect a home-tenant organizational account through the Power BI Microsoft connection, or run as an app registration with a Microsoft app credential, to list named workspaces, inspect reports and semantic models, execute DAX queries, request standard refreshes, and read refresh history. A Microsoft Graph connection cannot substitute for the Power BI connection or app credential. An app credential needs the Power BI tenant setting that allows service principals to use Power BI APIs and its service principal added to each workspace as a Member or Admin; DAX queries do not run as a service principal against semantic models with row-level security or SSO. Self-hosted installations use the shared Microsoft app registration and register /api/auth/oauth2/callback/microsoft-powerbi as a Web redirect URI. Workspace listing supports a result limit, offset, and OData filter; reports and semantic models return flat lists. Read-only models may contain only their ID and name, and paginated reports may omit their semantic-model ID. Missing optional fields are null and do not establish permission or feature availability. Keep results small with summaries or TOPN: provider JSON reads are limited to 20 MiB, and workflow tool responses have a stricter 10 MiB inline budget. My Workspace, cross-tenant guest configuration, Credential Groups, impersonation, enhanced refresh, report exports, dashboards, and triggers are outside this version.`,
0 commit comments