What OutreachFlow asks of your Microsoft 365 tenant, how to approve it, where the data goes, and how to remove it.
If an employee sees “Need admin approval” or “Approval required” when signing in to OutreachFlow, your tenant has not approved it yet: see Approval.
What it is
OutreachFlow is a Windows desktop app by DomusFlow BV, Belgium. A salesperson imports a list of contacts and writes a short series of mails; OutreachFlow sends them from that person's own Microsoft 365 mailbox, the follow-ups as replies in the same thread. It watches that person's Inbox and stops the series for a company as soon as anyone there answers.
It signs in as that person through Microsoft and acts only in that person's mailbox. It sends only the mails that person wrote, to the contacts that person imported: at most 50 a day per mailbox unless the person sets another number, two minutes apart, on the days and hours the person chose.
Permissions
One app registration in Microsoft Entra ID: OutreachFlow, multitenant, application (client) ID 9eeefc57-1e5d-44aa-8fe6-b6609894785a. Microsoft Graph, delegated permissions only:
- Mail.ReadWrite
- Creates the mails it sends in the user's mailbox, reads new mail in the user's Inbox to recognise replies, automatic replies and bounces, and deletes its own first mails that still wait at Microsoft when the user takes them back.
- Mail.Send
- Sends those mails as the user.
- User.Read
- Signs the user in and reads their name and address, to show the account.
- offline_access
- Keeps the user signed in, so the app needs no new sign-in each time it opens. OutreachFlow itself works only while it is open.
No application permissions and no client secret: OutreachFlow can only act as a signed-in user, in that user's own mailbox.
OutreachFlow and SearchFlow, also by DomusFlow, are separate registrations: approving one does not approve the other, and SearchFlow's stays read-only.
Approval
Under Microsoft's default consent settings, employees cannot approve mail permissions for an app from outside the company. An administrator approves OutreachFlow once, for the whole tenant; until then an employee without admin rights sees “Need admin approval” or “Approval required” at sign-in.
- On your own PC, open this link and sign in as a Global Administrator, or another role that may grant tenant-wide consent:
- Check the permissions Microsoft lists and click Accept.
- The browser then goes to
http://localhost/ and shows “This site can't be reached”. That is normal: the approval is done.
Employees then sign in without a consent screen.
Microsoft's page shows OutreachFlow as unverified: DomusFlow BV's publisher verification with Microsoft is not done yet.
Do not approve on an employee's PC through “Have an admin account? Sign in with that account” on Microsoft's sign-in page: OutreachFlow would then add your mailbox on that PC.
To check the approval: Entra admin center → Enterprise applications → OutreachFlow → Permissions.
Data
Stays on the PC
- The contact lists, the mails the user writes, the campaigns and the replies OutreachFlow read, in
%LOCALAPPDATA%\OutreachFlow in the user's profile. There is no central copy.
- The Microsoft sign-in tokens, in the same folder. They are used only with Microsoft and never sent to us.
The mails go from the user's mailbox to the recipients through Microsoft 365, like any mail the user sends. They do not pass through our server.
Sent to our server (searchflow-server.vercel.app)
- The app's log, every 5 minutes: the install id (a random id the app makes at first start), the app version, the signed-in accounts and the new log lines: what was sent and received when, counts and errors. Every e-mail address is cut to its domain in the app, before it leaves the PC, so the log tells which company, never who. The server keeps the log 14 days.
That server is shared by DomusFlow's apps; it keeps each app's logs apart. Nothing is sold or shared with anyone else. Privacy statement: outreachflow.be/privacy.
Revoking
- For everyone: Entra admin center → Enterprise applications → OutreachFlow → Properties → Delete. To block it but keep the entry, set “Enabled for users to sign-in?” to No instead.
- For some people only: in the same Properties, set “Assignment required?” to Yes and add the people who may use it under Users and groups; removing someone there ends their access.
OutreachFlow sends and reads nothing more once its current access token expires. First mails it already handed to Microsoft with a send time still go out at that time; until then they wait in the user's Drafts or Outbox and can be deleted there.
On a PC: Windows Settings → Apps → OutreachFlow → Uninstall removes the program. The data folder %LOCALAPPDATA%\OutreachFlow (lists, campaigns, sign-in tokens, logs) stays until it is deleted by hand.
Installer
- Windows 10 or 11. Download: outreachflow.be/start.
- Per user, no administrator rights: it installs to
%LOCALAPPDATA%\Programs\OutreachFlow, with a Start menu and a desktop shortcut. No service, no scheduled task, no startup entry.
- The installer is not code-signed yet, so the browser and Windows SmartScreen warn before it runs. Signing in DomusFlow BV's name is planned.
- It updates itself: at start and every 10 minutes it checks one fixed address (outreachflow-updates.vercel.app) for a newer version, downloads it in the background, checks its checksum and installs it silently, per user, at the next start.
- Its window shows a local page served on 127.0.0.1:8791; nothing listens on the network.
Questions: sales@domusflow.io.
DomusFlow BV, Knokke-Heist, Belgium, VAT BE 0750792272.