Microsoft Ads Integration
INTEGRATIONS · EXPERTINI ATS

Microsoft Ads Integration

Launch Microsoft Ads campaigns tied to your published job posts, straight from the ATS.

2 min read · Updated July 2026 · Expertini Editorial

Bing, Edge, and the wider Microsoft network reach an audience many recruitment campaigns ignore — often at lower cost per click precisely because fewer advertisers compete there. The Microsoft Ads Integration lets you launch campaigns for your published Expertini ATS jobs on that network directly from the ATS, using the job's own title, location, and apply URL as the campaign's foundation.

The gap this closes is single-channel dependence. Teams that advertise only where everyone else does pay peak prices for the same candidates. An ATS with Microsoft Ads integration makes the second-largest search network a two-minute decision instead of a separate project: the job is already written, the landing page is already live, and the applications land in the same hiring pipeline as every other source. The integration ships in your subscription — Microsoft bills your own advertising account, and Expertini charges nothing on top.

Watch the 30-second overview — no sign-up needed

01Campaigns built from job records

Select a published job and the integration carries its details into a Microsoft Ads campaign — no retyping, no mismatched URLs, no ads pointing at expired pages. Budget, bidding, and audience targeting remain yours to set in your own Microsoft Advertising account.

Managing ads where the jobs live also keeps campaigns honest: when the role closes in the ATS, you see immediately which spend no longer has a purpose.

02A different audience at different economics

The Microsoft network skews toward desktop and professional environments — a natural fit for many office-based and technical roles. Because competition is thinner than on the dominant network, budgets often stretch further. Running both networks from the same ATS lets you compare cost per application by source, using real pipeline data rather than each platform's own dashboard.

03Part of a full distribution stack

Paid campaigns are one layer. Underneath, every published job is submitted to Google for Jobs automatically, and programmatic distribution can push listings across 250+ Expertini country sites. Microsoft Ads becomes the precision instrument for roles that need extra demand — see pricing for what is included at each plan level.

Engineering notes

Platform architecture & operations

A1Connection architecture

The connection model for this integration is stated honestly on its card: where a public API exists it is used with your own account and consent, and where a vendor requires a partner agreement the page says so instead of showing a Connect button that cannot work.

Once available, credentials follow the platform standard: encrypted at rest, presence-flag display, immediate removal on disconnect.

A2Write semantics and data flow

Every data movement is an explicit action with a logged result. Writes happen on your click — or automatically only where you enabled a rule (auto-push on hire is off by default, per-provider). Reads — imports of people, accounts, or files — run when you press Import, deduplicate against what you already have (clients by name, people by email), skip rather than overwrite, and report created-versus-skipped honestly, which is why re-running any import is safe by design.

Each action writes a row to the app-activity journal (ats_app_activity): what ran, when, for which record, and the outcome — including the vendor's own error text verbatim when something fails. Usage reporting inside the ATS aggregates that same journal, so integration reporting and integration reality cannot diverge.

Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.

A3Operational considerations

Connections are organisation-level and gated to owner and admin roles; recruiters use the features a connection powers but cannot connect, disconnect, or reconfigure. Disconnecting removes stored credentials immediately and stops the dependent features visibly, not silently. Data already imported stays yours and editable.

Imported people arrive marked as imported with conservative privacy defaults — no consent is assumed for anyone who never filled in your application form, and retention defaults apply. Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.

A4Placement in the integration topology

This integration is live in the registry today. One connection per provider unlocks every feature it powers, and the topology grid below shows the neighbouring connectors in the same capability area — statuses come from the same registry that drives the in-app hub, so this page can never claim more than the product does. For anything the catalogue does not cover, Webhooks and Zapier are the generic, documented escape hatch.

Dependency map

Connection typestated per-vendor on the card
Secrets at restencrypted; UI shows presence flags, never values
Action journalats_app_activity — one row per action, vendor errors verbatim
Auto-push rulesoff by default, per-provider, every run logged
Registry statuslive

Interface blueprint

Structural schematic of the surface — panels, hierarchy, and interaction affordances. A contract, not a screenshot.
Connection card
● connected — presence flag
scopes: minimum required disconnect
Actions
push — explicit clickimport — deduplicated
Activity journal
Fig. 1 — Microsoft Ads Integration: structural interface schematic. Panels and states are the contract; data shown is placeholder.

Interaction flow — states, validations, feedback

Every state below is enforced server-side; the interface reports it, it doesn't decide it.
Connectowner/admin clicks Connect on the Connectors page
Vendor consentthe vendor's own screen lists the exact scopes
Token exchangeserver-side callback; secrets never touch the browser
Connectedencrypted store; card flips with presence flag
Explicit actionspush / import / schedule — each one journalled
Consent denied → the vendor's error code surfaces in a toast, namedPlatform keys missing → honest setup pointer, not a silent bounceToken expired → automatic refresh at the chokepointRefresh rejected → visible reconnect prompt, features never break silentlyPlan below minimum → lock card names the exact plan
Fig. 2 — interaction flow: navy = states, gold = server-enforced gates, green = confirmed outcomes; tags list the edge cases and their feedback.

Frequently asked questions

Do I need a Microsoft Advertising account?
Yes. You connect your own account and Microsoft bills your ad spend directly. Expertini adds no markup and no per-campaign fee — the integration itself is included in your subscription.
Is Microsoft Ads worth it for recruitment?
For many roles, yes — competition is lower than on the dominant search network, so clicks can cost less, and the audience skews toward desktop professional use. The pipeline data in your ATS will tell you how it performs for your specific roles.
Can I run Google Ads and Microsoft Ads together?
Yes. Both connectors are included, both work from the same published job records, and applications from both land in the same pipeline so you can compare sources fairly.
What happens to ads when I close a job?
The campaign lives in your Microsoft account, so you stop it there — but because the job and the campaign are linked in the ATS, a closed role is an immediate, visible prompt to end the spend.

At a glance

  • Launch campaigns from published jobs in minutes
  • Reach the Bing and Edge search audience
  • Often lower cost per click than crowded networks
  • Your own Microsoft account and direct billing
  • Compare sources with real pipeline data
  • No markup, no add-on fees

See microsoft ads integration on your own hiring.

Bring a real job description to a 30-minute demo — free trial included.

Book a demo
Expertini AI
Online now
Hi! I'm Expertini's AI Product Expert. Ask me anything about our solutions, get guidance on any of our Hiring Tools, or just tell me what you're trying to do — I'll point you in the right direction. For account-specific issues, email support@expertini.com.