Deploy the add-in for your firm

How IT deploys Blast Audit from the Microsoft 365 admin center, what to do about error 53003, and how licences work on terminal servers.

If your firm blocks add-ins from the Microsoft store, users cannot install Blast Audit themselves. A Microsoft 365 administrator can deploy it to the whole firm, or to some groups, from the Microsoft 365 admin center.

Deploy from the Microsoft 365 admin center

These steps are done by your Microsoft 365 administrator. Microsoft documents them in Deploy add-ins in the Microsoft 365 admin center.

  1. In the Microsoft 365 admin center, go to Settings > Integrated apps.
  2. Click Get apps and search for Blast Audit.
  3. Choose who gets the add-in: everyone, specific users, or groups.
  4. Accept the permissions and finish the deployment.

The Blast Audit tab then appears in Excel for those users. Microsoft says this can take several hours. Users may need to close and reopen Excel.

What your IT team needs to know:

ItemValue
NameBlast Audit
PublisherNextbp
Microsoft Marketplace IDWA200007951
HostExcel only
PermissionRead and write the open workbook

If your firm filters outbound web traffic, ask support for the list of domains the add-in needs to reach.

Deployment does not create accounts

Deploying the add-in puts it in Excel. Each person still needs a Blast Audit account and a seat in your organisation:

  1. An owner or admin of your Blast Audit organisation invites them from Users in the dashboard. See Start a trial and invite your team.
  2. They accept the invitation and sign in from the add-in with the invited email.

If users see a Microsoft access error

Error code 53003 means Microsoft Entra Conditional Access blocked the request. It happens before Blast Audit loads. Your administrator can find the policy in the Entra sign-in logs using the request ID, correlation ID and timestamp shown on the error screen. Deploying from the admin center, as above, avoids the user-side store install.

Terminal servers and remote desktops (RDS, RDP)

We have not tested Blast Audit on Remote Desktop Services or Citrix, and we do not list them as supported environments. If you use it there and something does not work, write to support and tell us which environment you use.

This is how licences and sign-in behave on a shared Windows server, where each person uses Blast Audit in their own Windows session:

  • Deploy or install the add-in for the Excel used on the server, the same way as above.
  • Each person signs in with their own Blast Audit account. A licence belongs to one person.
  • One licence can be active on two devices at the same time. A third device gets License already in use. Close Excel or the Blast Audit pane on another device, then retry. When Excel is closed on a device, its slot is freed after about 10 minutes.
  • The add-in keeps its sign-in and device identifier in the user's Office storage. If your server resets user profiles when people sign out, they will have to sign in to Blast Audit again in each session, and each session may count as a new device.

Still stuck?

Email the team with what you tried and, if you can, a screenshot of what you see.

Email support