Tables
Connect to load tables
Select a table
Select a table to see its columns
Record Exporter for Dataverse
About Record Exporter for Dataverse
This application lets you connect to a Microsoft Dataverse environment, browse tables and columns, and export data to CSV — all from your browser. No server-side processing is involved in data retrieval.
🔒 Authentication & Authorization
Sign-in is handled entirely by Microsoft’s MSAL (Microsoft Authentication Library) running in your browser. Your credentials are never seen or stored by this application — they are entered directly into Microsoft’s login page via a secure pop-up.
- The app uses the OAuth 2.0 Authorization Code flow with PKCE, the industry-standard for browser-based apps.
- Access tokens are scoped exclusively to your Dataverse environment and are held only in browser memory.
- The app never stores passwords, secrets, or refresh tokens on disk.
🔁 How Data Flows
- Browser ↔ Microsoft Entra ID: Authentication tokens are requested directly from Microsoft’s identity platform.
- Browser ↔ Dataverse: All API calls (table metadata, record queries, exports) go directly from your browser to the Dataverse OData endpoint using your token. No intermediary server processes or relays this data.
- CSV export: Data is converted to CSV entirely in-browser and downloaded to your device. Nothing is uploaded anywhere.
👁 Who Has Access to Your Data?
- Only you. Data flows directly between your browser and Microsoft’s Dataverse APIs. No third party — including the developers of this tool — can see, intercept, or store your data.
- The web host serves only static files (HTML, CSS, JS). It has no backend, no database, and no logging of your Dataverse data.
- Shareable links encode only table/column/filter configuration — never actual record data or credentials.
🛠️ Application Security
- The Azure AD App Registration used by this tool is configured as a public client (SPA) — it contains no client secret.
- All communication uses HTTPS/TLS encryption.
- The application requests only the minimum permissions needed:
user_impersonationon your Dataverse environment. - Source code is open and auditable on GitHub.
📑 Auditing & Usage Tracking for Administrators
Because this tool authenticates through Microsoft Entra ID and calls the Dataverse OData API directly, all usage is recorded by Microsoft’s standard audit infrastructure. System administrators can track who used this tool, when, and what data was accessed:
- Microsoft Entra ID Sign-in Logs — Every authentication is recorded. Go to the Entra admin center → Identity → Monitoring & health → Sign-in logs. Filter by the application name or client ID to see all sign-ins to this tool, including user, time, location, and device.
- Dataverse Auditing — If auditing is enabled in your environment, Dataverse logs every data read performed via the API. In the Power Platform admin center, select your environment → Settings → Audit and logs → Audit summary view. You can also enable per-table and per-column audit settings under Settings → Audit and logs → Entity and Field Audit Settings.
- Microsoft Purview Audit — For organizations using Microsoft 365 E5 or Purview, unified audit logs capture Dataverse API activity. Search in the Purview compliance portal under Audit, filtering for Dynamics 365 / Dataverse activity.
- Entra ID App Activity — Usage and consent records for this app registration are available in the Entra admin center under Identity → Applications → Enterprise applications. Select this app to view sign-in activity, permissions granted, and user assignments.
To restrict access to this tool, administrators can use Conditional Access policies in Entra ID or limit the app registration’s user assignment to specific groups.
