Yes. BulkSignature works with Outlook on the web (OWA) and with Microsoft 365 F3 licenses, and no one needs to install anything on their computer.
Microsoft 365 F3 is designed for frontline teams. F3 users email from Outlook on the web and the Outlook mobile app, because the desktop Outlook apps aren't included in F3. BulkSignature fits this setup: it reads each person's details from Microsoft Entra ID (formerly Azure AD) and adds signatures through the BulkSignature add-in for Outlook. Your IT team sets it up once, and every F3 user who is assigned a signature gets the correct company signature.
How BulkSignature Adds Signatures
BulkSignature adds signatures through its Outlook add-in, which your IT team deploys centrally from the Microsoft 365 admin center:
Outlook on the web: When you start a new message, reply or forward, your signature is already in the message body, so you can see exactly what recipients will receive while you write.
Outlook mobile app (iPhone and Android): Your signature is added automatically when you start a new message, reply or forward.
The add-in picks the right version of your signature: Reply/Forward for replies and forwards, Internal for new messages addressed only to people at your own email domain, and Primary for everything else. If your company hasn't set up a separate Reply/Forward or Internal version, your Primary signature is used.
BulkSignature doesn't use Exchange mail flow rules (transport rules) or connectors, and your email isn't routed through BulkSignature's servers.
Why F3 Licenses Work with BulkSignature
Microsoft 365 F3 includes a 2 GB Exchange Online mailbox (the Exchange Online Kiosk plan) and the web and mobile versions of Outlook. That's everything the BulkSignature add-in needs: it runs in Outlook on the web and in the Outlook mobile app, and Microsoft supports central add-in deployment for F3 users. Each person's details (such as name, job title, department, phone numbers and office location) come from your Microsoft Entra ID directory, so F3 users get the same personalized signature as everyone else.
Using Microsoft 365 F1? F1 licenses don't include the right to use an Exchange mailbox, so F1 users can't send email from Outlook and don't get an email signature.
Compatibility at a Glance
Requirement | What F3 includes | BulkSignature | Details |
Outlook on the web | Included | SUPPORTED | Your signature appears in the compose window when you start a message |
Outlook mobile app (iPhone and Android) | Included | SUPPORTED | Your signature is added automatically when you start a message |
Outlook desktop apps (classic Outlook, new Outlook for Windows, Outlook for Mac) | Not included | NOT REQUIRED | Nothing is installed on users' computers |
Outlook on the web in a phone's browser | Not supported by Microsoft | NOT SUPPORTED | Use the Outlook mobile app on phones |
Directory sync | Microsoft Entra ID | SUPPORTED | Job titles, departments and contact details sync once a day |
Deployment | Microsoft 365 admin center | SUPPORTED | IT deploys the add-in once through Integrated apps |
Do employees need to install anything?
No. Your IT administrator deploys the BulkSignature add-in centrally from the Microsoft 365 admin center. Microsoft can take up to 24 hours to roll it out. After that, your signature appears automatically whenever you start a new message, reply or forward.
What happens when an F3 user sends an email from their phone?
In the Outlook mobile app for iPhone or Android, BulkSignature adds your company signature automatically when you start a new message, reply or forward. Keep the app up to date. On a phone, the add-in picks the signature version for you; there's no BulkSignature button for choosing a different one.
Add-ins don't run in Outlook on the web opened in a phone's browser, and Microsoft doesn't support using Outlook on the web on phones. Use the Outlook mobile app instead.
Tip: If you reply from the bottom of a message in the Outlook mobile app, your signature is added but may not be visible right away. Expand the reply to full screen to see it.
Can F3 users use the new Outlook for Windows?
No. Microsoft doesn't allow Frontline licenses (F1 and F3) in the desktop Outlook apps, including the new Outlook for Windows. F3 users email from Outlook on the web and the Outlook mobile app, and BulkSignature works in both.
Do we need Exchange mail flow rules or connectors?
No. BulkSignature doesn't use mail flow rules (transport rules) or connectors. Don't add a mail flow rule that appends a signature for your F3 users, or their emails will end up with two signatures.
For Employees: Finding Your Signature in Outlook on the Web
Once your IT team has deployed the BulkSignature add-in:
Go to Outlook on the web and sign in with your work account.
Select New mail, or reply to or forward a message. Your company signature is already in the message body, along with any banner or disclaimer your company includes in it.
To use a different version of your signature, select BulkSignature on the Message tab of the ribbon. If you don't see it, select Apps, then BulkSignature. In the panel, find the version you want (Primary, Reply/Forward or Internal) and select Use signature.
Write your email and select Send.
Don't see your signature or the BulkSignature button? Contact your IT administrator. The add-in may not be assigned to your account yet, Microsoft may still be rolling it out (this can take up to 24 hours), or no signature may be assigned to you in BulkSignature.
For IT Admins: Setup Checklist
Connect Microsoft 365. In BulkSignature, go to Settings > Integrations > Microsoft 365 and sign in with a Microsoft 365 admin account. BulkSignature imports your users from Microsoft Entra ID and keeps their details in sync once a day (Settings > General > Daily Employees Sync, on by default).
Check your directory data. Make sure Job title, Department, Business phone, Mobile phone and Office location are filled in for your F3 users in Microsoft Entra ID. BulkSignature fills each person's signature from these fields, so details that are empty can't appear.
Deploy the add-in and grant admin consent. The Microsoft 365 card in Settings > Integrations shows the next action to take. Follow it until the card says the add-in is deployed to everyone:
Open Microsoft 365 Admin Center: in Settings > Integrated apps, open the BulkSignature listing, select Get it now, choose who gets the add-in (we recommend Entire organization), accept the permissions and finish the deployment.
Set up the add-in or Grant admin consent: approve the add-in's permissions for your organization. See the admin consent article below.
If you deploy the add-in to a group instead of your entire organization, use a Microsoft 365 group, a distribution list or a mail-enabled security group (non-mail-enabled security groups aren't supported), and add your F3 users to that group directly, because members of nested groups don't receive the add-in. Microsoft can take up to 24 hours to roll the add-in out.
Assign a signature. In BulkSignature, create a signature and assign it to everyone or to your F3 users (or a group they belong to). Users without an assigned signature don't get one.