Monthly interaction quota and what counts

What it does

Every outbound message Journeys sends consumes one interaction against a monthly tenant quota. You don't buy that quota directly — it's derived from your interacted people entitlement at a fixed multiple, and it resets on the first of each month.

Key facts

The monthly interaction quota is ten times your interacted people entitlement. 10,000 interacted people means 100,000 interactions per month at tenant level.
The multiple is fixed. There is no separate "buy more interactions" SKU — the only way to raise the monthly ceiling is to raise the interacted people entitlement.
Interactions are not tied to individual people. With 100,000 interactions you can send all of them to one person or spread them across a hundred thousand; Microsoft tracks the tenant total, not per-person usage.
The quota resets on the first day of each month and unused allowance does not roll over.
The exact system events counted are EmailSent, EmailCcSent, SmsSent, PushNotificationSent, VoiceChannelSent and CustomChannelSent. A CC'd email counts as its own interaction.
Inbound activity does not count. Form submissions, opens, clicks and website visits consume no interaction quota.
Third-party and custom channels count. Messages sent through an integrated SMS provider or a custom channel still register against the quota even though Microsoft isn't delivering them.
Usage is visible at Settings > Quota limits, with charts for monthly interaction usage and annual interacted people usage. The same page separates this environment's usage from the "Other orgs in your tenant" total.
In-app notifications fire as the organisation approaches its paid quota and again when it exceeds it.
The quota page also surfaces adjacent consumption that is not the interaction quota: Litmus inbox previews (pre-seeded monthly capacity, resets monthly), free ACS text messages for US-based instances, and paid text messages where the allowance actually lives with your SMS provider.

When to use / skip

This is the number that gets a project in trouble, so it's worth understanding before the first journey goes live rather than after. The interacted people meter is easy to reason about — how many people do we market to. The interaction quota is the one that bites, because sending frequency is a marketing decision made monthly by people who never see the licence.

A client sending a monthly newsletter to their whole base uses roughly one interaction per person per month and will never come near the ceiling. A client running transactional-style trigger journeys, order confirmations, multi-step nurtures and an SMS reminder on top can chew through ten sends per person without anyone noticing. If the programme design looks like the second one, size the interacted people entitlement from the interaction volume divided by ten, not from the audience size.

Configuration decisions

Which channels are in scope, and therefore how many interactions a typical customer receives per month. SMS and push are cheap to add to a journey and each send costs an interaction.
Whether to size entitlement for the peak month or accept that one month a year runs hot and plan a top-up.
Whether CC recipients are used on email — each one is a chargeable interaction, so a habit of CCing an account manager multiplies volume.
Frequency capping in the consent and journey settings, as a control on interaction burn as well as on customer experience.
Whether sandbox journeys are allowed to send at production volume during testing, given the quota is shared tenant-wide.
Who watches the quota page and at what point in the month they escalate.

Gotchas

The quota is tenant-wide, not per environment. A sandbox soak test in the last week of the month can push production over the line.
Nothing in the quota is per-person, so a badly built re-entry loop that sends the same contact fifty emails costs fifty interactions and shows up as volume, not as a data quality problem.
Custom channel sends count. Teams sometimes assume that because Microsoft isn't delivering the message, it's free. It isn't.
Litmus previews and text message allowances sit on the same screen but are entirely different meters. Running out of Litmus previews has nothing to do with your interaction quota, and the paid SMS number shown in-app has to be reconciled against the provider's own figures.
Unused quota evaporates monthly. There's no banking a quiet January to cover a busy November.
Trials and preview environments have their own separate limits — trials cap at 1,000 emails a month — so a number observed during a trial tells you nothing about a paid tenant.

Consultant notes

Do the arithmetic with the client in the room: expected sends per person per month, times audience, divided by ten, equals the interacted people entitlement they need. It lands much better than quoting the multiple.
Demo the quota page during UAT, not at go-live. Marketing operations need to recognise the screen before the first notification appears.
Push back on "let's add SMS to every journey as well" until someone has costed the extra interactions and the provider's own per-message charges.
Check the "other orgs in your tenant" figure before signing off a capacity purchase — on multi-environment clients, a surprising share of the burn is often non-production.
Anything commercial beyond the mechanics — how overage is actually settled, what the contract says — is in the Dynamics 365 Licensing Guide and with the client's account team, not on Microsoft Learn. Say so rather than guessing.

Worth another look if the 10x multiple changes, or when Microsoft adds new sending channels to the counted event list.