Add-in Deployment Troubleshooting

Troubleshoot common issues with deploying the fixSignatures Outlook add-in via Microsoft 365 Centralized Deployment.

Add-in Not Visible in Outlook

Propagation Delay (Most Common)

After deployment, add-ins can take 24-72 hours to appear in all users’ Outlook clients. This is a Microsoft 365 limitation, not specific to fixSignatures.

What to do:

• Wait at least 24 hours after deployment
• Have users sign out and back in to Outlook
• For Outlook Web: clear browser cache
• For Outlook Desktop: restart the application

Check Deployment Scope

Verify the add-in is deployed to the correct users:

1. Go to Microsoft 365 Admin Center
2. Navigate to Settings → Integrated apps
3. Click on fixSignatures
4. Check the “Users assigned” section
5. Ensure the affected user is included (either directly or via a group)

Verify Deployment Status

Check that the deployment completed successfully:

1. In Microsoft 365 Admin Center → Integrated apps
2. Find fixSignatures in the list
3. Status should show “Deployed”
4. If it shows “Failed” or “Pending”, try removing and re-deploying

Add-in Shows Error on Load

Manifest URL Not Accessible

The add-in needs to load its manifest from our servers:

1. Copy the manifest URL from Settings → Microsoft 365 Setup
2. Paste it in a browser and try to access it
3. If it doesn’t load, there may be a network/firewall issue
4. Check if your organization blocks external URLs

Subscription Inactive

The add-in requires an active subscription:

1. Log in to fixSignatures
2. Go to Billing & Subscription
3. Verify your subscription is active
4. Resolve any payment issues if needed

Add-in Loads But No Signature Appears

If the add-in icon is visible but signatures don’t insert:

User Not Enabled

1. In fixSignatures, go to Settings → Signature Users
2. Find the user
3. If status shows “Disabled”, click Enable

No Signature Assigned

1. Go to Signatures
2. Verify at least one signature is enabled
3. Check that a default signature is set, or the user has a group assignment

API Connectivity Issue

The add-in needs to communicate with fixSignatures servers:

• Check browser developer console (F12) for network errors
• Verify your organization’s firewall allows connections to fixSignatures domains
• Try from a different network to rule out local issues

Users Can’t See Add-in After Assignment

Group Membership Sync

If you deployed to a group, verify the user is in that group:

1. Go to Azure Portal → Groups
2. Find the group used for deployment
3. Check members to confirm the user is included
4. If recently added, wait for group membership to propagate

License Requirements

Some Microsoft 365 plans have add-in restrictions:

• Verify users have licenses that support Outlook add-ins
• Business Basic and above typically support add-ins
• Some education or government plans may have restrictions

Re-deploying the Add-in

If you need to start fresh:

1. Go to Microsoft 365 Admin Center → Integrated apps
2. Find and select fixSignatures
3. Click Remove app
4. Wait 1 hour for removal to propagate
5. Re-deploy following the deployment guide

Platform-Specific Issues

Outlook Desktop (Windows)

• Requires Outlook 2016 or later
• Office must be updated to latest version
• Try restarting Outlook after deployment
• Check File → Office Account for updates

Outlook Desktop (Mac)

• Requires Outlook for Mac 16.x or later
• Some add-in features may differ from Windows
• Check for updates via Mac App Store or Microsoft AutoUpdate

Outlook Web (OWA)

• Works in modern browsers (Chrome, Edge, Firefox, Safari)
• Clear browser cache if add-in doesn’t appear
• Try incognito/private window to rule out cache issues

Outlook Mobile (iOS/Android)

• Mobile add-in support is limited
• Not all add-in features work on mobile
• Ensure Outlook app is updated to latest version

Getting Help

If you’ve tried all the above and still have issues:

1. Note the exact error message (if any)
2. Note which Outlook client is affected (Web, Desktop, Mobile)
3. Take a screenshot of the Integrated Apps deployment status
4. Contact support with these details