Intune Report Export Web App

Export Intune reports via Microsoft Graph with live polling and CSV table rendering. Includes a lightweight proxy (for blob downloads), a public status page, and a hidden admin panel with short‑lived audit logging.

Quick Start

1. Install deps:

npm install

2. Create .env from .env.example and set a strong admin path + pass.

3. Start the server:

npm start

4. Open:

http://localhost:3000

If you host the UI separately, set config.json:

{
  "proxyBaseUrl": "http://localhost:3000"
}

Azure App Setup (Summary)

• SPA app registration
• Redirect URI:

http://localhost:3000

• Delegated permissions:
  • Reports.Read.All
  • DeviceManagementManagedDevices.Read.All

Report Names

This app does not hardcode report names. The UI links to the Intune reports list so users can self‑serve.

Pages

• App: http://localhost:3000
• Status UI: http://localhost:3000/status
• Status JSON: http://localhost:3000/status.json
• Admin: http://localhost:3000/<ADMIN_PATH>?code=<ADMIN_PASS>

Admin Panel

Shows backend status, audit events, and audit settings.

Configuration

.env

ADMIN_PATH=/control-CHANGE_ME
ADMIN_PASS=CHANGE_ME_STRONG
PUBLIC_PROXY_URL=

• ADMIN_PATH: hidden admin route
• ADMIN_PASS: required access code
• PUBLIC_PROXY_URL: set when frontend is hosted elsewhere

config.json

{
  "proxyBaseUrl": "https://your-backend.example.com"
}

Audit Logging

• Default retention is 5 minutes.
• Storage mode can be set in the Admin panel:
  • memory (in‑memory only)
  • file (persists to audit-log.json)

Notes

• Node is used only for the proxy + audit + admin.
• Report data is fetched via the proxy to avoid CORS issues.

Troubleshooting (Short)

• 401 Unauthorized: check Graph permissions + admin consent.
• CORS error: ensure the proxy server is running.
• Admin panel 404: verify ADMIN_PATH + ADMIN_PASS, then restart server.