Netstrata Add-in Manager
Dashboard 🪄 New Add-in 📁 Files 📝 Manifest 🚀 Deploy ⚙ Settings
Loading...

📖 Help & Guide

📊 Dashboard

The Dashboard shows all your add-ins as cards. Each card displays:

  • Add-in name, version, GUID
  • Status badges (Enabled/Disabled, exchange/centralized)

Click any add-in card to open its detail page with Exchange deployment status, Azure URL health, and quick links to edit/deploy.

Detail pages load instantly — data is cached server-side.

📁 File Manager

Upload and manage files in $web Azure Storage:

  1. Click Upload — select a file
  2. Choose folder: Root or assets/
  3. Accepted: .html .js .css .png .xml .json .svg

Click the ℹ info button next to any file name to see its purpose, configuration details, and dependencies.

⚠ Cannot delete: taskpane.html, commands.html, bulk.html, msal-browser.min.js

📝 Manifest Editor

Edit your add-in's manifest.xml:

  • Edit the XML directly in the textarea
  • Bump Version auto-increments version number
  • Validate runs schema compliance check via office-addin-manifest
  • Save Draft saves to local database only — safe for work-in-progress
  • Deploy to Cloud uploads the manifest to Azure Storage

🔒 Deploy to Cloud requires validation — you must get a green "✅ Manifest is Valid" before deploying. If content changes after validation, re-validation is forced.

Version format: 1.0.0.0 (4-part). Backup stored in backup/.

🚀 Deploy

Push your manifest to Exchange Online (full deployment):

  1. Edit & validate your manifest on the Manifest page
  2. Deploy to Cloud on the Manifest page to sync Azure Storage
  3. Come here to manage assigned users (add/remove)
  4. Click Deploy Now to push to Exchange

This runs: validate (disk) → backup → upload to Azure → deploy to Exchange

You can also click Update Users Only to change user assignments without re-deploying the manifest.

⚠ Propagation takes 5-15 minutes for OWA, up to 24h for classic Outlook.

🪄 New Add-in Wizard

Create a brand-new Outlook add-in from scratch:

  1. Identity — name, description, GUID
  2. Configuration — review generated manifest
  3. Users — assign users (resolved to display names automatically)
  4. Deploy — push to Exchange

Uses the same Azure Storage, MSAL auth, and icon assets as the existing add-in.

User emails are automatically resolved to display names via Entra ID before deployment.

⚙ Settings

Admin only. Manage platform users:

  • Add User — create new accounts with optional admin access
  • Edit — change username or full name
  • Reset Password — set a new password for any user
  • Delete — remove user accounts

🔒 The root admin user cannot be deleted or edited by other admins.

New users can be flagged as Admin (full access) or User (read-only).

🔧 Troubleshooting

  • Add-in not showing in OWA?
    Wait 5-15 min, sign out/in of OWA, hard refresh.
  • Validation fails?
    Check XML syntax. Version must be 4-part. GUID must be valid.
  • Deploy fails?
    Check Exchange connectivity. Ensure GUID doesn't conflict with existing app.
  • URL check fails?
    Verify files are uploaded in File Manager. Check Azure Storage.
  • MSAL auth error (AADSTS700016)?
    Verify Entra ID app registration exists. Contact administrator.
  • SMATA search fails?
    Check network connectivity to api.smata-test.cloud.netstrata.com.au.
  • Add-in not showing in OWA?
    Wait 5-15 min, sign out/in of OWA, hard refresh.
  • Validation fails?
    Check XML syntax. Version must be 4-part. GUID must be valid.
  • Deploy fails?
    Check Exchange connectivity. Ensure GUID doesn't conflict with existing app.
  • URL check fails?
    Verify files are uploaded in File Manager. Check Azure Storage.