Grok Bot Privacy Mode: what it does, how to change it, and what that means for MSPs

Risograph still life of a closed envelope and a glass paperweight on textured paper

Privacy Mode is the Cursor setting MSPs ask about first, and it is also the setting they most often misunderstand. People hear “privacy” and assume customer Microsoft 365 data will not be stored, will not leave Australia, or will never appear in a chat history. That is not what the documentation says.

Privacy Mode is about training and about how model providers retain prompts. It is not a promise that Grok Bot keeps nothing. Grok Bot needs cloud storage in order to work. If you cannot explain that difference to a customer, you are not ready to point a Bot at their tenant.

This post stays with what Cursor publishes. I will not describe my own account settings, or invent a click path that is not in the official docs. Where the docs leave a gap, I will say to check with Cursor. I covered the broader security picture, including the shared computer, in What MSPs should understand about Grok Bot security and customer Microsoft 365 data. This one is narrower: Privacy Mode itself, how to change it, and what that means if you use Grok Bot with customer data.

What Privacy Mode is, and what it is not

Cursor’s Data Use & Privacy Overview is the plain description. If you enable Privacy Mode in Cursor’s settings, customer data is not used for training by Cursor. Cursor says it maintains zero data retention (ZDR) agreements with model providers, and those providers will not store or train on your data. There is an exception you should not skip: subject to their policies, model providers, including Cursor, may run risk or abuse classifiers, and if a prompt or conversation triggers those detectors, data may be stored for investigation and later deleted under the provider’s retention policy.

If you turn Privacy Mode off, the same page says Cursor may use and store codebase data, prompts, editor actions, code snippets and other code data and actions to improve features and train models. Some inference providers may also temporarily access and store model inputs and outputs to improve inference performance, then delete that data after use.

That is the switch that matters for an MSP. With Privacy Mode on, the published commitment is no training, plus ZDR with providers, plus the classifier exception. With it off, prompts and related data may be used to improve and train.

The Grok Bot security page says Privacy Mode applies, that while a member is on a team the team’s privacy mode governs them, and that with Privacy Mode enabled, customer data is not used for training. The teams page adds that Cursor enforces this on its servers, and that when the setting cannot be verified, the system defaults to not training. The approvals, security and privacy help article says training opt-out follows the applicable Cursor account and privacy settings.

Cursor’s general privacy help article is a little more cautious on one point. It says Privacy Mode in the Cursor editor prevents your code from being used for training, and that Grok Bot runs on a separate product surface with its own data flows, then points you back to the data-use page and the sub-processor list. I am not going to pretend those two wordings are identical. For Grok Bot work, I treat the Grok Bot security and teams pages as the product-specific source, and I still tell customers to read the data-use page and, if they need a contractual assurance, to check with Cursor and look at the applicable Data Processing Agreement.

Privacy Mode does not mean “nothing is stored”. Grok Bot requires data storage. The security documentation is explicit about what persists. Each member’s computer keeps files, browser sessions and anything saved in the browser on a durable disk across sessions. Idle hibernation is not deletion. Deleting a Bot does not remove those shared files or sessions. Connector tokens stay on Cursor’s backend, not on the computer. Vault holds logins and, if you save them, payment cards, and it covers the whole account. Chats are part of the product; you come back to them. Cursor also says the production control plane is covered by daily encrypted backups. Under the Data Processing Agreement, data is deleted or returned within 30 days of written direction after the service ends. If you do not have a DPA, follow the Privacy Policy and ask Cursor how deletion works for your plan. To request deletion of Grok Bot computer files that contain personal data, Cursor’s privacy help says to contact support with your account email, the agent name and a description of the files.

Privacy Mode also does not move the computer out of the United States, and it does not replace least privilege, approvals or a cleanup habit. Those are separate controls.

Legacy Privacy Mode is a different setting

There are two privacy settings, and the names have been easy to mix up. Cursor’s documentation usually says Privacy Mode and Privacy Mode (Legacy), or Legacy Privacy Mode. In the week of 5 October 2026, Cursor’s web release notes said the privacy settings now read “Privacy Mode (no training)” and “Legacy (no storage)”. That naming is the clearest short explanation I have seen: one setting is about training, the other is about refusing cloud storage.

Grok Bot needs cloud storage, so Legacy Privacy Mode is not supported. The get started guide says that if your account is on Privacy Mode (Legacy), the app asks you to switch to Privacy Mode first. On a team, a team admin changes the team’s privacy setting. The teams documentation is blunt: move off Privacy Mode (Legacy), because that setting blocks Grok Bot entirely, and you are prompted to change it before enabling. Check the privacy setting in Team Settings.

If you are still on Legacy because you wanted no storage, understand the trade-off: that setting will not run Grok Bot. Current Privacy Mode is the no-training setting that still allows the storage Grok Bot needs. Cursor’s Privacy and Data Governance page describes it as the setting that keeps your code from being used for training, with ZDR guarantees for team members when it is enabled at the team level. Privacy Mode (Legacy) also forces Action Recording off. Action Recording is an Enterprise control, off by default, and is not a reason to stay on Legacy.

Who can set it, and how the plans differ

This is a Cursor account or team setting, not a per-Bot switch.

On an individual plan, Cursor’s Enterprise comparison describes Privacy Mode as a user choice. You should not assume it is on. Check it.

On a team, Cursor’s privacy help says Privacy Mode is enabled by default for all team members, and that it is on by default for Enterprise teams. Teams and Enterprise admins can enforce it organisation-wide so members cannot disable it. Cursor’s enterprise comparison lists that org-wide enforcement for both Teams and Enterprise. Still verify. Defaults are only useful if they are still in place on your team.

While a member is on a team, the team’s privacy mode governs them. That matters if someone also has a personal Cursor account. Cursor’s data governance documentation mentions an MDM option, Allowed Team IDs, which is designed to stop people signing into personal accounts on corporate devices. Check with Cursor whether that is available on your plan.

I have not seen a documented Privacy Mode toggle in the Grok Bot app itself. The documented Grok Bot Settings tabs are General, Computer, Vault, Usage and Billing, and Updates. Privacy Mode does not appear in that list. The approvals help article says privacy and data-sharing choices are managed through Cursor account settings and, when required, the Grok Bot access flow, which matches the Legacy prompt described above.

How to check it, and how to change it

For an individual account, Cursor’s privacy help gives this path in the Cursor app, not the Grok Bot app:

1. Open Cursor Settings with Cmd + Shift + J on a Mac, or Ctrl + Shift + J on Windows or Linux.

2. Click General in the sidebar.

3. Toggle Privacy Mode on.

If you cannot find that toggle, do not invent another path. Check in your Cursor account or team settings, and use the privacy help and data-use pages as the source.

For a team, Cursor’s Privacy and Data Governance page gives this path:

1. Go to your team dashboard.

2. Navigate to Settings.

3. Enable Privacy Mode for the team.

4. Optionally enforce it so members cannot disable it.

The teams documentation points to the same place in fewer words: check the privacy setting in Team Settings. The help article also says admins can enforce it organisation-wide via cursor.com/dashboard.

If Grok Bot is prompting you to leave Legacy Privacy Mode, follow that access flow, or ask a team admin to change the team’s setting. Do not try to “make Legacy work” with Grok Bot. The product does not support it.

One official caution when you create a team from a personal plan: the same October 2026 release notes say that a “Share Cursor Analytics” checkbox sets the new team’s privacy setting, and that Privacy Mode stays on unless you check it. If you are an MSP creating a team, read that box before you tick it.

What changes when you switch

Turn Privacy Mode on, and the published effect is that customer data is not used for training, and ZDR with model providers applies, subject to the abuse-classifier exception. Non-ZDR models, where a provider requires retention, are designated as such or need an admin to opt in. Cursor documents some models, such as the Claude Fable family, as working this way. Check the current models with data retention notes rather than treating this as a living list. Grok Bot also manages model selection and does not offer a customer-facing picker, so this is a team and provider question, not a per-chat toggle.

Turn Privacy Mode off, and Cursor may use and store prompts and related data to improve features and train models, as quoted above. For an MSP holding customer Microsoft 365 data in those prompts, that is a material change. I would not turn it off on an account that has ever been used with customer data, unless the customer has agreed and you have a reason that survives a privacy conversation.

Switching off Legacy and onto current Privacy Mode is what unblocks Grok Bot. It does not, by itself, delete data that is already stored, and I have not seen documentation that says turning Privacy Mode on wipes existing chats, memory or computer files. If you need a deletion or a confirmation of what happens to data already held, check with Cursor. The documented cleanup you can do yourself is still the practical one: pause routines, sign out of sites on the shared computer, remove sensitive files from `/workspace`, revoke connectors, and use Vault or a Secure Form rather than pasting secrets into chat.

Enforcing Privacy Mode at the team level means members cannot disable it. That is the right default for an MSP team that will see customer data.

What this means for MSPs

Customer Microsoft 365 data that a Bot reads can end up in a chat and on the shared computer even when Privacy Mode is on. Privacy Mode addresses training. It does not keep that copy inside the customer’s tenant. You still decide what the Bot is allowed to read, what you allow it to write into `/workspace`, and how long those files stay there. All of a user’s Bots share one computer, so a second Bot is not a privacy boundary for those files. If two customers’ data must never sit on the same disk, you need a separate Cursor user, as I set out in the earlier security post.

Tell customers the truth in plain language. Something like: we use Grok Bot with Privacy Mode enabled, which, according to Cursor, means customer data is not used for training, and model providers operate under zero data retention agreements, with a stated exception for abuse and safety classifiers. The Bot still stores chats and working files because the product requires storage. Grok Bot computers run in the United States. If we need a written residency commitment, that is a separate Cursor program, not the Privacy Mode toggle.

On residency, be precise. The security page and the security FAQ say Grok Bot computers run in the United States. Cursor also has a US-only data residency program. When it is enabled for a team, inference, processing and storage for Grok Bot stay in the US. That is a wider processing and storage commitment for enrolled customers, including backups; it is not automatic, it is enabled per team, and Cursor documents a pricing uplift and some exclusions, such as connectors. Contact Cursor if you need to enrol. Do not tell a customer the data never leaves Australia.

On contracts, Cursor’s privacy help is clear enough for a first pass. The Data Processing Agreement governs how Cursor processes personal data under enterprise contracts, for Teams and Enterprise customers. If you are on an individual plan, the DPA does not apply and data handling follows the Privacy Policy. Check what you actually have, and do not quote a DPA you have not signed. Current sub-processors are listed at trust.cursor.com/subprocessors.

Enterprise plans have extra controls beyond Privacy Mode, including audit logs, Action Recording, network allowlists, enforced Auto-review and related admin tooling. Those are Enterprise only. Privacy Mode itself is not an Enterprise-only feature. You can have the training commitment without those extra logs, and you should not tell a customer you have a SIEM feed unless your plan actually includes it.

What I would put in a customer conversation is short. Privacy Mode is on, or we will not use this account for your data. It is a no-training setting, not a no-storage setting. The computer is in the United States. We use least-privilege access, keep secrets out of chat, clean up working files, and will not turn Privacy Mode off without telling you.

Example prompts and Bot instructions

These are examples. They do not replace the setting, and a Bot cannot prove that Privacy Mode is on. You check that yourself in Cursor or in Team Settings.

Example: a profile instruction that treats customer data as temporary working material

You work on a single named customer at a time. Treat anything you read from Microsoft 365, email or files as customer data. Do not write customer data, secrets, tenant identifiers or mailbox content into memory, and do not ask me to paste passwords, client secrets or certificates into this chat. If a secret is required, use a Secure Form or Vault. Keep working files in a clearly named folder and be ready to list and remove them when I ask. If you are asked to confirm whether Privacy Mode is on, tell me you cannot certify that setting and that I should check it in Cursor account or team settings.

Example: asking a Bot to report what it is holding, not to invent a privacy setting

Before we start, list any files in /workspace that look like they belong to a customer, and tell me whether this chat already contains secrets or tenant identifiers. Do not guess whether Privacy Mode is on. I will check that in Cursor settings. Do not copy customer content into memory.

Example: cleaning up after a customer engagement

Pause any routines for this customer. List the connectors, browser sessions and files in /workspace that appear to belong to this engagement. Do not delete yet. I will tell you what to remove, and I will sign out of the admin centre and revoke access myself where needed. Do not keep a summary of customer data in memory after we finish.

Example: a boundary in a live request

Draft a short internal note from yesterday’s Service health for this tenant. Do not email anyone, do not change any policy, and do not store the raw export after you have drafted the note. Ask before saving anything outside this chat.

A short MSP checklist

  • I have checked Privacy Mode in Cursor Settings or in Team Settings, and I have not assumed it is on.
  • If I am on a team, Privacy Mode is enabled and, if my plan allows it, enforced so members cannot turn it off.
  • I am not on Privacy Mode (Legacy). I understand that setting blocks Grok Bot because Grok Bot requires storage.
  • I can explain to a customer, in plain language, that Privacy Mode is a no-training setting, not a no-storage setting, and that Grok Bot computers run in the United States.
  • If a customer needs a written residency or DPA commitment, I have checked what Cursor actually offers for our plan, including the US-only residency program, rather than inventing one.
  • Customer data in chats and on the shared computer is treated as a copy we are responsible for. I have a cleanup step, and I have not treated separate Bots as a privacy boundary.
  • Secrets stay in Vault or a Secure Form, not in the transcript.
  • I have not turned Privacy Mode off on an account used with customer data, and I know that doing so may allow prompts to be used to improve and train models.
  • I have read Cursor’s current data-use, Grok Bot security and privacy pages, not only this post.

The practical takeaway

Privacy Mode is worth turning on, and on a team it is worth enforcing, before a Bot ever reads a customer’s tenant. It answers the training question customers will ask. It is not an answer to every privacy question they will ask. Storage, location, access and cleanup are still yours to manage.

Check the setting. Change it if it is wrong. Tell the customer what it does and what it does not do. Then use least privilege, approvals and a clean computer, so the training commitment is not the only control you are relying on.

Who Owns the Agent When the Employee Walks Out the Door?

A professional leaving an office tower at dusk, glowing threads trailing from her briefcase back to the building

Here’s a question I don’t think many businesses have asked yet. When you hire your next person, will they be allowed to bring their own agents with them? And when someone leaves, will you let the agents they built in your business walk out the door too?

For years we’ve treated a worker’s toolkit as personal. Their know-how, their shortcuts, their way of working. Agents blur that line badly. An agent can hold skill, but it can also hold memory, data and relationships. That makes the answer far less obvious than it first appears.

The toolkit versus the tenant

I think the cleanest way to start is to split an agent into two parts.

The first part is the pattern. The prompts, the instructions, the way someone has learned to break a job down and hand it to AI. That’s skill. It lives in their head as much as anywhere, and I don’t believe a business can or should claim it. A good tech who has learned how to direct agents well will carry that ability to their next role, the same way they carry their troubleshooting instincts.

The second part is the data. An agent built in Copilot Studio inside your Microsoft 365 tenant, grounded on your SharePoint libraries and connected to your systems, belongs to the tenant. So does what Copilot remembers about how a person works. Microsoft stores Copilot memory in a hidden folder in the user’s Exchange mailbox, inside your tenant, and admins can find it with Purview eDiscovery. That’s a pretty strong hint about where ownership sits.

I wrote recently about the mystery of personal SharePoint skills, which end up stored in a user’s OneDrive. Personal in name, but still sitting in the company’s tenant. Expect a lot more of that.

Memory is where it gets messy

Picture a consultant who has spent two years working with an agent. It knows her clients, their quirks, which contracts are touchy and which projects ran late. Now she moves to a competitor. Should that memory go with her?

My view is no, and not because the business is being greedy. That memory is tangled up with client data, confidentiality obligations and, in many cases, data residency requirements. You can’t neatly pull “how she works” out of “what she knows about our customers”. Until the tools can genuinely separate the two, the memory has to stay.

Treat BYO agents like BYOD

Bringing your own agent in the other direction feels a lot like the early days of bring-your-own-device. The answer then wasn’t a flat yes or no. It was policy, identity and control. Agents need the same treatment. Whose identity does it run under? What data can it reach? Where does what it learns end up? If you can’t answer those, the agent shouldn’t touch your tenant.

What I’d do now

None of this is legal advice, and your lawyer will have views. But there are practical steps any SMB or MSP can take today:

  • Write a simple agent policy covering who can build, bring and share agents.
  • Keep an inventory of every agent, with a named human owner.
  • Add agents and AI memory to your offboarding checklist, right next to mailbox and device handover.
  • Update employment contracts to say what’s portable and what stays.
  • Decide upfront that skills and prompt patterns travel, while data and memory stay put.

The people who learn to work well with agents will be worth more wherever they go. That’s fine. Let them take the skill. Keep the data. Just make sure you’ve written down which is which before someone hands in their notice.

Pressing Record in Australia: Who Needs to Say Yes?

Cartoon of colleagues around a meeting table smiling and agreeing, with a closed laptop and a simple microphone on the table

The short version

Recording a meeting is useful. Minutes, a replay for whoever was on leave and an AI summary are all real benefits. But in most of Australia you can’t just press record, or let an AI note-taker into the room, without everyone’s consent. The rules differ by state and territory, and the penalties for getting it wrong can be serious. Even where the law lets a participant record, trust is the thing that gets damaged.

My recommendation is simple. Have one official recording, run by the organiser, with consent built into the booking or invite and announced at the start. No personal or third-party recorders, AI bots or wearables unless the organiser has agreed. Sample wording is further down.

This is general information, not legal advice. I’m not a lawyer. If it matters, get advice for your situation.

Why this is everyone’s problem now

AI note-takers have made recording effortless. Microsoft 365 Copilot in Teams, Otter, Fireflies, Zoom recording, phone voice memos and even AI wearables will happily capture a whole conversation and ship it off to a cloud service. In an MSP or small business that covers internal meetings, client calls and the awkward conversations about incidents and mistakes. If someone discovers a bot or a phone quietly recording, that trust goes.

What the law says, state by state

There’s no single national recording law. It’s mostly state and territory surveillance-device legislation, plus Commonwealth rules on telecommunications. Broadly, Victoria, Queensland and the NT let a participant record a private conversation without the others’ consent. SA and WA generally require everyone’s consent. NSW, Tasmania and the ACT generally require consent too, with a narrow exception for recording for your own personal use that isn’t shared. Consent can be express or implied.

JurisdictionStatuteCan a participant record without others’ consent?Key exceptionPenalty (where verified)
NSWSurveillance Devices Act 2007 (s7)Generally noPersonal use only (not communicated or published to non-parties), or reasonably necessary to protect lawful interestsUp to 100 penalty units or 5 years (individual); 500 penalty units (company)
VicSurveillance Devices Act 1999 (s6)Yes – participant recording isn’t caught by s6Communicating or publishing a private conversation is regulated separately (s11)Not verified for publication
QldInvasion of Privacy Act 1971 (s43)Yes – s43(2)(a) exempts a partyPublication is regulated separately (ss44-45)40 penalty units or 2 years (using a device on a conversation you’re not part of)
SASurveillance Devices Act 2016 (s4)No – all principal parties must consent, expressly or impliedlyReasonably necessary to protect lawful interests; public interestUp to $15,000 or 3 years (individual); $75,000 (body corporate)
WASurveillance Devices Act 1998 (s5)NoLawful interests and similar exceptionsUp to $5,000 or 12 months (individual); $50,000 (body corporate)
TasListening Devices Act 1991 (s5)Generally no (NSW-style)Personal use only / lawful interests40 penalty units or 2 years (secondary source, not verified)
ACTListening Devices Act 1992 (s4)Generally no (NSW-style)Personal use only / lawful interests50 penalty units (secondary source, not verified)
NTSurveillance Devices Act 2007 (s11)Yes – offence only applies if you’re not a partyPublication is regulated separately (s15)250 penalty units or 2 years (non-party recording)
CthTelecommunications (Interception and Access) Act 1979 (ss6-7)Not an issue for a party recording at their own end, generallyInterception of a live communication over a telecoms system without the knowledge of the person making it is prohibitedUp to 2 years

Check these before relying on them. Section numbers and penalties come from secondary sources that summarise the statutes. The Tasmanian and ACT penalties are unverified, and so are the Victorian, Queensland and NT penalties for publishing a recording. Check the current legislation before you rely on any of it.

Two more traps:

  • Publishing is a separate issue. Even where you can lawfully record, communicating or publishing the recording to others can be an offence or need consent. Sharing a recording or transcript on LinkedIn, in a Teams chat or with an AI vendor can be the real problem.
  • Mixed locations. If you’re in Victoria, someone’s in Perth and someone’s in Sydney, it’s not clear which law applies. The safest approach is to assume the strictest one applies, which means getting everyone’s consent.

In person, online and ‘private conversation’

The surveillance device laws are about ‘private conversations’. Broadly, a conversation isn’t private if all the parties ought reasonably to expect it might be overheard by someone else. A large open session might arguably fall on that side. A small team meeting or a client call almost certainly doesn’t. I wouldn’t rely on that argument. A court looks at the circumstances, and it’s untested for meetings like yours.

The rules apply equally to a phone on the table, a wearable and a bot that joins your Teams call. The device is a ‘listening device’ whatever it looks like.

Commonwealth: the TIA Act and the Privacy Act

  • TIA Act: it prohibits intercepting a live communication passing over a telecommunications system without the knowledge of the person making it. A participant recording at their own end isn’t usually treated as interception. Whether a bot that joins a call as a participant is different hasn’t been tested, as far as I know.
  • Privacy Act: it applies to ‘APP entities’, which are generally businesses with turnover over $3 million (plus some smaller ones, such as health providers) and government agencies. The small business exemption is still in force as at October 2026 according to secondary sources, though reform has been proposed. Many MSPs are under the threshold, but many of their clients and some vendors aren’t.
  • OAIC guidance: it says meeting recordings and AI transcripts are personal information. Collect only what’s reasonably necessary, tell people, consider opt-outs, and destroy or de-identify what wasn’t needed, such as a personal chat or confidential client details.
  • Statutory privacy tort: since 10 June 2025 there’s a tort for serious invasions of privacy. I haven’t verified how it applies to small operators or to recordings.

The AI note-taker problem

The recording is only half of it. An AI tool adds questions that an old-fashioned voice memo never did:

  • Third-party storage: your colleagues’ and clients’ words now sit on a vendor’s servers.
  • Training: does the vendor use the audio or transcripts to train its models? Some do, so check the terms.
  • Cross-border: the data is probably processed outside Australia.
  • Confidentiality: people discuss client names, incidents and commercial details, which may breach NDAs or client contracts.
  • Voiceprints: some tools build speaker profiles, which is biometric-style data.
  • Sharing: some tools email a summary to every attendee, or publish a link, automatically.

This is already in the courts overseas. In re Otter.AI Privacy Litigation in the US alleges Otter’s Notetaker recorded meetings without all participants’ consent and used the data for training. In August 2026 a federal court held Otter could plausibly be treated as a third-party eavesdropper because it keeps and uses recordings for its own purposes. That’s US law, not ours, but it shows the risk.

There are workplace consequences too. The Fair Work Commission has accepted covert recording as a valid reason for dismissal (Schwenke v Silcar [2013] FWC 4513). NSW also needs 14 days’ written notice for camera, computer or tracking surveillance of employees, and the ACT has a notice and consultation regime. If you run staff meetings through an AI recorder, check them.

A simple approach for MSPs and small business

The cleanest fix is to separate the organiser’s official recording from everyone else’s. The organiser decides, tells everyone, gets consent and controls where the recording lives and who sees it. An individual’s own recorder or bot has a separate vendor, separate retention and nobody else’s consent. In SA, WA and (mostly) NSW, Tasmania and the ACT that’s where someone can get into trouble, even if they only meant it as private notes.

  1. Write a short recording policy. Plain English (sample below).
  2. Get consent in the invite or booking. Say the meeting will be recorded, why, who sees it and how to opt out.
  3. Announce it at the start. Silence after a clear announcement may amount to implied consent, but express consent, such as a ticked box or a Teams consent prompt, is better.
  4. Make it visible and offer opt-outs. Use the recording indicator, say it out loud, and let people keep their camera off or ask in chat.
  5. One official recording. The organiser shares the transcript or summary afterwards, so nobody needs their own recorder.
  6. Set retention, deletion and access. Where it’s stored, how long it’s kept, who can view it, and how someone asks for deletion.
  7. Control who joins. See the Teams notes below. Zoom shows participants a consent prompt when recording starts.
  8. If you find an unauthorised recording, stay calm. Politely ask for it to be stopped, ask what’s been captured and where it’s stored, and ask for deletion and no sharing. Don’t confront anyone publicly or take their device. If it’s serious or has been shared, get advice.

What Microsoft 365 gives you in Teams

If you manage the tenant, two Teams meeting policy settings are worth knowing. Both are admin-level policies, not per-meeting switches, and both match Microsoft Learn.

  • Manage external bots and their access to meetings. Teams detects external bots such as note-takers and holds them in the lobby until the organiser explicitly admits them. “When detected, require approval before joining” is the default. Microsoft says some bots may not be detected, so it doesn’t replace a policy. It also suggests letting only organisers and co-organisers admit people from the lobby.
  • Require participant agreement for recording and transcription. It’s off by default. Switch it on and, once recording or transcription starts, everyone else is muted with camera and sharing off until they answer Yes or No. A No means a view-only experience. The person who starts the recording is treated as having consented, and the choices appear in the attendance report. It’s the closest thing Teams has to a tick-the-box consent.

Sample wording

(a) Invite or booking notice

This meeting will be recorded (audio, video and chat) by the organiser so that people who can’t attend can catch up and so we can produce notes and an AI-generated summary. The recording is stored in [location], kept for [90 days], and available only to [who]. If you’d prefer not to be recorded, email [organiser] before the meeting and we’ll make arrangements, such as keeping your camera off or asking questions in chat. Please don’t use your own recording tools, AI note-takers or bots without the organiser’s agreement. By attending after reading this notice, you agree to be recorded.

(b) Start-of-meeting script

Before we start: this session is being recorded by us, the organisers, for notes and an AI summary that we’ll share afterwards. If you don’t want to be recorded, please say so now or message [organiser] in chat, and we’ll sort it out. Please don’t run your own recorder or AI note-taker. We’ll share the official transcript and summary. If anyone is uncomfortable at any point, we can pause the recording. Is everyone happy to proceed?

(c) Short recording policy

  • Only the organiser makes the official recording of a meeting.
  • Attendees must not record audio or video by any means (phone, laptop, wearable, AI note-taker or bot) without the organiser’s agreement and the consent of everyone present.
  • Attendees are told about the recording in the invite and at the start of the meeting, and can opt out.
  • The organiser shares the transcript or summary with attendees. It isn’t shared outside the meeting without the consent of the people in it.
  • Recordings are stored in [location], kept for [period], and deleted on request where practical.
  • Unapproved bots will be removed. If an unauthorised recording is found, the organiser will ask for it to be stopped and deleted.

What I haven’t verified

  • Section numbers and penalties come from secondary sources, not the statutes themselves.
  • The Tasmanian and ACT penalties are unverified.
  • The Victorian, Queensland and NT penalties for publishing a recording are unverified.
  • Whether a bot that joins a call counts as ‘interception’ under the TIA Act is untested, as far as I know.
  • I haven’t verified how the statutory privacy tort applies to small operators or to recordings.

Sources

General information only, not legal advice. Laws change and details vary by situation, so check the current legislation or get advice before relying on this.

Intune compliance policies + Conditional Access integration

image

Most people I speak to think the work of locking down devices in Microsoft 365 is creating the Intune compliance policy. They tick the boxes — BitLocker on, minimum OS, no jailbreaks — hit Save, and walk away feeling secure.

They aren’t.

A compliance policy on its own does precisely nothing to a sign-in. It’s a label. Intune looks at a device, decides “compliant” or “not compliant”, and writes that state back to Entra ID. That’s it. Nothing is blocked. Nothing is challenged. The policy is information, not enforcement.

The enforcement lives somewhere else entirely. It lives in Conditional Access.

If you’re not wiring those two things together, you’ve done half a job. And the half you skipped is the half that actually protects the tenant.

What is an Intune compliance policy, really?

Think of a compliance policy as a health check that runs on the device and ships the verdict back to your tenant. Encrypted? Patched? Joined to your tenant? Defender running? Out comes a true/false, and Entra ID writes it onto the device record.

That verdict is now available as a signal. Anything that can read Entra signals — and Conditional Access is the big one — can use it to make access decisions.

So the compliance policy is the sensor. Conditional Access is the gate. You need both, or you have neither.

Step-by-Step: wiring compliance to Conditional Access

Portal only. No PowerShell. This is what I do on every Business Premium tenant I touch.

Fix the tenant default first

Open the Intune admin center, go to Devices > Compliance > Compliance policy settings.

Find the setting Mark devices with no compliance policy assigned as. It ships set to Compliant.

Change it to Not compliant. Save.

That one setting is the difference between “any device in my tenant counts as good” and “a device has to earn it”. You’d be amazed how many tenants I audit where this is still on the default.

Build the compliance policy

Same portal. Devices > Compliance > Policies > Create policy. Pick Windows 10 and later (start there — do iOS and Android next).

Use the settings catalog options to set sensible rules — require BitLocker, a minimum Windows build, Defender real-time protection on, Defender signatures up to date. Don’t try to be heroic on day one. Set what you can defend with a straight face. Microsoft’s own walkthrough is the canonical reference.

In Actions for noncompliance, do not leave the default of “Mark device noncompliant: 0 days”. Give yourself a grace window — 1 to 3 days — and add a Send email to end user action a day earlier. People deserve a heads-up before they’re locked out of email.

Assign to a pilot user group. Not all users. A pilot group.

Build the Conditional Access policy

Now flip over to the Entra admin center: Entra ID > Conditional Access > Policies > New policy.

Users: include your pilot group. Exclude your break-glass account. Always.

Target resources: All resources.

Grant: Require device to be marked as compliant. Save.

And here’s the critical bit — set Enable policy to Report-only. Not On. Report-only.

Users:       Pilot group
Exclude:     Break-glass account
Resources:   All resources
Grant:       Require device to be marked as compliant
Enable:      Report-only

Notice what’s missing? MFA. That belongs in a separate policy. One policy, one job. Stack them, don’t fuse them.

Watch report-only for a week

Sign-in logs > Report-only tab. You’re looking for users who would have been blocked and shouldn’t have been — usually a missing enrollment, a personal device that needs the App Protection path instead, or a service account.

When the report-only data is clean, flip the toggle to On. Microsoft’s compliant-device CA template walks the same path.

Why this actually changes behaviour

“But MFA is already on. Isn’t that enough?”

It isn’t. MFA proves the user. Compliance + CA proves the device. Token theft doesn’t care about your MFA prompt — it cares whether the device the token landed on is one you trust. This is the bit MFA-only tenants are missing.

It also collapses three messy conversations down to one. “Is this laptop ours? Is it patched? Is it encrypted?” All of it rolls into one signal — compliant, or not. Conditional Access reads that one signal and decides. No more inventory spreadsheets. No more guessing.

And if you’re an MSP, this is the most defensible artefact you can show a client during an incident. The device was non-compliant. Access was blocked. That’s a finished sentence.

A compliance policy isn’t there to make a list of bad devices. It’s there to make sure they never sign in.

Intune Filters vs Assignment Groups: Stop Treating Them as Interchangeable

image

If your Intune estate has grown past a couple of hundred devices, you’ve probably built a forest of dynamic groups that only you understand. You don’t need another group. You need a filter. Here’s where each one earns its keep, and where MSPs keep getting the split wrong.

The mental model

Groups answer who the policy targets. Filters answer which subset of that assignment it actually applies to at evaluation time. A group is resolved at assignment and refreshed on Entra’s schedule. A filter is evaluated per device, per policy, at the point of applicability. That timing difference is the entire reason filters exist — and the reason swapping one for the other silently changes behaviour.

Use groups for ownership of the assignment (department, site, client tenant, pilot ring). Use filters for device traits that change underneath you: OS version, model, enrollment profile, personal vs corporate, join type.

Prerequisites people miss

  • Filters only work on managed devices and managed apps — the supported workload matrix matters. Not every policy type honours filters, and app assignment filters for MAM are a different object from device assignment filters. Check the reference before assuming your policy can be filtered.

  • Dynamic device groups require at least one Entra ID P1 licence in the tenant. Business Premium covers you, but confirm before promising dynamic membership to an M365 Standard client.

  • The “All users” and “All devices” virtual groups bypass normal targeting logic. If a client’s environment feels “haunted”, check whether a legacy assignment is hitting All devices with no filter.

Where to configure

In the Intune admin center, filters live under Tenant administration → Filters. Build the rule, pick the platform, and save — the filter itself has no targets. You apply it at assignment time on any supported policy (Devices → Configuration → your profile → Assignments → Edit filter).

Groups are managed in the same console under Groups, but remember these are Entra ID security groups — any change you make is tenant-wide, not Intune-only.

The rollout pattern that actually works

  1. Ring by group, scope by filter. Three device groups (Pilot, Early, Broad) assigned by user or device attribute. Apply the same policy to all three with different filters (e.g. deviceOwnership -eq "Corporate" plus osVersion -startsWith "10.0.22").

  2. Exclude filters beat exclusion groups. If you’re excluding kiosks from a CA-backed compliance policy, a filter keyed on enrollmentProfileName is faster to audit than a stale exclusion group nobody refreshes.

  3. Name everything for future-you. FLT-Win11-Corp-NotKiosk beats Filter1. Same for groups: prefix by purpose (INT- for Intune-only, SEC- for CA), include platform, include intent.

  4. Test in report-only. Every new filter goes onto one profile assigned to a lab group first. Confirm the Assignment status report matches expectation before widening.

The pitfalls that will bite you

  • Filter evaluation is not group membership. A filter excluding “personal” devices won’t retroactively remove a policy from a device that was previously “corporate” until the device checks in and the assignment re-evaluates. Plan for the delay during ownership changes.

  • Negation logic is deceptively literal. -notEquals treats a null property as “not equal”, so filters on sparsely populated properties (custom enrollment profile names, model on older hardware) can match devices you didn’t intend. Test with -eq plus include/exclude to lock it down.

  • Overlapping filters on the same assignment don’t AND. If you add a filter and also use include/exclude groups, precedence rules apply — exclude always wins, then filters, then includes. Map this out before complaining about “Intune not applying my policy.”

References

Data Loss Prevention (DLP) in M365 Business Premium – Comprehensive Guide

bp1

Data Loss Prevention (DLP) in Microsoft 365 Business Premium is a set of compliance features designed to identify, monitor, and protect sensitive information across your organisation’s data. It helps prevent accidental or inappropriate sharing of sensitive data via Exchange Online email, SharePoint Online sites, OneDrive for Business, and other services[1][1]. By defining DLP policies, administrators can ensure that content such as financial data, personally identifiable information (PII), or health records is not leaked outside the organisation improperly. Below we explore DLP in depth – including pre-built vs. custom policies, sensitive information types and classifiers, policy actions (block/audit/notify/encrypt), user override options, implementation steps, best practices with real-world scenarios, and common pitfalls with troubleshooting tips.


Key Features of DLP in Microsoft 365 Business Premium

  • Broad Protection Scope: Microsoft 365 DLP can monitor and protect sensitive data across multiple locations – including Exchange email, SharePoint and OneDrive documents, and Teams chats[1][1]. This ensures a unified approach to prevent data leaks across cloud services.
  • Content Analysis: DLP uses deep content analysis (not just simple text matching) to detect sensitive information. It can recognize content via keywords, pattern matching (regex), internal functions (e.g. credit card checksum), and even machine learning for complex content[1][2]. For example, DLP can identify a string of digits as a credit card number by pattern and checksum validation, distinguishing it from a random number sequence[2].
  • Integrated Policy Enforcement: DLP policies are enforced in real-time where users work. For instance, when a user composes an email in Outlook or shares a file in SharePoint that contains sensitive data, DLP can immediately warn the user or block the action before data is sent[2][2]. This in-context enforcement helps educate users and prevent mistakes without heavy IT intervention.
  • Built-in Templates & Custom Rules: Microsoft provides ready-to-use DLP policy templates for common regulations and data types (financial info, health info, privacy/PII, etc.), and also allows fully custom policy creation to meet organisational specifics[2][2]. We detail these options further below.
  • User Notifications (Policy Tips): DLP can inform users via policy tips (in Outlook, Word, etc.) when they attempt an action that violates a DLP policy[2]. These appear as a gentle warning banner or pop-up, explaining the policy (e.g. “This content may contain sensitive info like credit card numbers”) and guiding the user on next steps before a violation occurs[2]. Policy tips raise awareness and let users correct issues themselves, or even report false positives if the detection is mistaken[2].
  • Administrative Alerts & Reporting: All DLP incidents are logged. Admins can configure incident reports and alerts – for example, send an email to compliance officers whenever a DLP rule is triggered[3][3]. Microsoft 365 provides an Activity Explorer and DLP alerts dashboard for reviewing events, seeing which content was blocked or overridden, and auditing user justifications[1][1]. This helps monitor compliance and refine policies continuously.
  • Flexible Actions: DLP policies can take various protective actions automatically when sensitive data is detected. These include blocking the action, blocking with user override, just logging (audit), notifying users/admins, and even encrypting content or quarantining it in secure locations[1][3]. These actions are configurable per policy rule, as discussed later.
  • Integration with Labels & Classification: DLP in Microsoft Purview integrates with Sensitivity Labels (from Microsoft Information Protection) and supports Trainable Classifiers (machine learning-based content classification). This means DLP can also enforce rules based on sensitivity labels applied to documents (e.g. “Highly Confidential” labels)[4], and it can leverage classifiers to detect content types that are not easily identified by fixed patterns.

M365 Business Premium Licensing: Business Premium includes the core DLP capabilities similar to Office 365 E3[5]. This covers DLP for Exchange, SharePoint, OneDrive, and Teams. Advanced features like endpoint DLP or advanced analytics are generally part of higher-tier (E5) licenses, although Business Premium organisations can still use trainable classifiers and other Purview features in preview or with add-ons[1][5]. For most small-to-midsize business needs, Business Premium provides robust DLP protections.


Pre-Built DLP Policy Templates vs. Custom Policies

Microsoft 365 offers a range of pre-built DLP policy templates to help you get started quickly, as well as the flexibility to create fully custom DLP policies. Here’s a comparison of both approaches:

Policy Type Description & Use Cases Pros Cons
Pre-Built Templates
Microsoft provides ready-to-use DLP templates addressing common regulatory and industry scenarios. For example:

    • U.S. Financial Data – detects info like credit card and bank account numbers (PCI-DSS).

 

    • U.S. Health Insurance Act (HIPAA) – detects health and medical identifiers.

 

    • EU GDPR – detects national ID numbers, passport numbers, etc.

 


Many others cover financial, medical, privacy, and more for various countries. Each template includes predefined sensitive information types, default conditions, and recommended actions tailored to that scenario. Administrators can select a template and adjust it as needed.



    • Quick Start: Fast to deploy compliance policies without deep expertise – just choose relevant template(s).

 

    • Best Practices: Encodes Microsoft’s recommended patterns, e.g., thresholds and actions, for that data type or law.

 

    • Customisable: You can modify any template – add/remove sensitive info types, tweak rules, or change actions to fit your organisation.

 

 



    • Broad Defaults: May be overly inclusive or not perfectly tuned, leading to false positives.

 

    • Limited Scope: Each template is focused on a specific regulation – may require multiple policies or significant tweaking for broader needs.

 

    • Globalization: Many templates are region-specific – ensure alignment with your jurisdiction and data types.

 

 

Custom Policies
You can build a DLP policy from scratch or customise a template. This involves defining your own rules, conditions, and actions to suit unique requirements – e.g., detecting proprietary project codes or internal-only data. You select the sensitive info types, patterns, or labels and configure rule logic manually. Microsoft also supports importing policies from external sources or partners.


    • Highly Tailored: Address specific business needs or unique sensitive data not covered by templates.

 

    • Flexible Conditions: Combine conditions in ways templates can’t – e.g., requiring multiple data types together.

 

    • Scoped Enforcement: Target policies to specific departments or projects using policy targeting.

 

 



    • More Effort & Expertise: Requires deep understanding of DLP components and thorough setup/testing.

 

    • No Starting Guidance: Creation from scratch can be error-prone without built-in thresholds or examples.

 

    • Maintenance: Needs ongoing tuning as data changes; no Microsoft baseline – fully managed by admin team.

 

 

Using Templates vs Custom: In practice, you can mix both approaches. A common best practice is to start with a template close to your needs, then customise it[2][2]. For example, if you need to protect customer financial data, use the “U.S. Financial Data” template and then add an extra condition for a specific account number format your company uses. On the other hand, if your requirement doesn’t fit any template (say you need to detect a confidential project codename in documents), you would create a custom policy from scratch targeting that. Microsoft 365 also lets you import policies (XML files) from third parties or other tenants if available, which is another way to get pre-built logic and then adjust it[2].

In the Microsoft Purview compliance portal’s DLP Policy creation wizard, templates are organised by categories (Financial, Medical, Privacy, etc.) and regions. The admin simply selects a template (e.g. “U.S. Financial Data”) and the wizard pre-populates the policy with corresponding rules (like detecting Credit Card Number, ABA Routing, SWIFT code, etc. shared outside the organisation) and actions (perhaps notify user or block if too many instances)[3][3]. You can then review and modify those settings in the wizard’s subsequent steps before saving the policy.

Summary: Pre-built DLP templates are great for quick deployment and covering standard sensitive data, while custom DLP policies offer flexibility for specialised needs. Often, organisations will use a combination – e.g. enabling a few template-based policies for general compliance (like GDPR or PCI-DSS) and additional custom rules for their particular business secrets.


Sensitive Information Types (SITs) and Trainable Classifiers

At the core of any DLP policy is the definition of what sensitive information to look for. Microsoft’s DLP uses two key concepts for this: Sensitive Information Types (SITs) and Trainable Classifiers.

Sensitive Information Types (SITs)

A Sensitive Information Type is a defined pattern or descriptor of sensitive data that DLP can detect. Microsoft 365 comes with a large catalog of built-in SITs covering common data like: credit card numbers, Social Security numbers (US SSN), driver’s license numbers, bank account details, passport numbers, health record identifiers, and many more (including country-specific ones)[6][6]. Each SIT definition typically includes:

  • Pattern/Format: for example, a credit card number SIT looks for a 16-digit pattern matching known card issuer formats and passes a Luhn check (checksum) to reduce false matches[2]. A Social Security Number SIT might look for 9 digits in the pattern AAA-GG-SSSS with certain exclusions.
  • Keywords/proximity: some SITs also incorporate keywords that often appear near the sensitive data. For instance, a SIT for medical insurance number might trigger more confidently if words like “Insurance” or “Policy #” are nearby.
  • Confidence Levels: SIT detection can produce a confidence score. Microsoft defines low, medium, high confidence thresholds depending on how many matches or supporting evidence is found. For example, finding a 16-digit number alone might be low confidence (could be a random number), but 16 digits + the word “Visa” nearby and a valid checksum = high confidence of a credit card. DLP policies can be tuned to act only on certain confidence levels.

Using SITs in Policies: When creating DLP rules, an admin will select which sensitive info types to monitor. You can choose from the library of built-in types – e.g., add “Credit Card Number” and “SWIFT Code” to a rule that aims to protect financial data[6]. You can also adjust instance counts (how many occurrences trigger the rule) – for example, allow an email with one credit card number but if it contains 5 or more, then treat it as an incident[5].

Custom Sensitive Info Types: If you have specialized data not covered by built-ins, Microsoft Purview allows creation of custom SITs. A custom SIT can be defined using a combination of:

  • Patterns or Regex: e.g., define a regex pattern for an employee ID format or a product code.
  • Keywords: specify words that often accompany the data.
  • Validation functions: optionally, use functions like Luhn checksum or keyword validation provided by Microsoft if applicable. For example, you might create a custom SIT for “Project X Code” that looks for strings like “PROJX-[digits]” and perhaps requires the keyword “Project X” nearby to confirm context.

Creating custom SITs requires some knowledge of regular expressions and content structure, but it greatly extends DLP’s reach. Once defined and published, custom SITs become available just like built-in ones for use in DLP policies.

Trainable Classifiers

Trainable Classifiers are a more advanced feature where machine learning is used to recognize conceptual or context-based content that isn’t easily identified by a fixed pattern. Microsoft Purview includes some pre-trained classifiers (for example, categories like “Resumes”, “Source Code”, or “Sensitive Finance” documents), and also allows admins to train their own classifier with sample data[7].

A trainable classifier works by learning from examples:

  • The admin provides two sets of documents: positive examples (which are definitely of the target category) and negative examples (which are similar in context but not of the target category)[7][7]. For instance, if training a classifier to detect “HR Resumes”, you’d feed it many resume documents as positives, and maybe other HR documents (policies, cover letters, etc.) as negatives.
  • Microsoft’s system will analyze the textual patterns, structure, and terms common to the positive set and distinct from the negative set, thereby learning what constitutes a “Resume” in general (for example, presence of sections like Education, Work Experience, and certain formatting).
  • Training Requirement: You need a substantial number of samples – typically at least 50 well-chosen positive samples and at least 150 negatives to get started, though more (hundreds) will yield better accuracy[7]. The system will process up to 2,000 samples if provided, to build the model.

After training, you test the classifier on a fresh set of documents to ensure it correctly identifies relevant content. Once satisfied, the classifier can be published and used in DLP policies just like an SIT. Instead of specifying a pattern, you would configure a rule like “if content is classified as Resume Documents (classifier) with high confidence, then apply these actions.”

When to use classifiers: Use trainable classifiers when the sensitive content cannot be easily captured by regex or keywords. For example, distinguishing a source code file from any other text file – there’s no fixed pattern for “source code” but a machine learning classifier can recognize code syntax structures. Another example is identifying documents that look like contracts or CVs; these might not have unique keywords but have overall similarities that a classifier can learn. Note: Trainable classifiers are more commonly associated with broader Purview content classification (for labeling or retention); in DLP they are an emerging capability (Microsoft announced support for using trainable classifiers in DLP policies in recent updates).

Sensitive Info Type vs Classifier: In summary, SITs are rule-based (pattern matching) and are great for well-defined data like ID numbers, whereas classifiers are ML-based and suited for identifying categories of documents or free-form content. DLP can leverage both: for example, a DLP policy might trigger on either a specific SIT or a match to a classifier (or both conditions).

To implement these:

  • Identifying SITs: In the compliance portal under Data Classification, you can view all Sensitive Info Types. Microsoft provides definitions and even testing tools where you can input a sample string to see if it triggers a given SIT pattern. This helps admins understand what each SIT looks for. Identify which ones align with your needs (financial, personal data, etc.) and note any gaps where you may need custom SITs.
  • Training Classifiers: Under Data Classification > Classifiers, you can create a new trainable classifier. Provide the example documents (often by uploading them to SharePoint or Exchange as indicated) and follow the training wizard[7][7]. This process can take time (hours to days) to build the model. Once ready, test it and then use it by adding a condition in a DLP policy rule: “Content is a match for classifier X.”

Example: Suppose your organisation wants to prevent leaked source code files via OneDrive or Email. There’s no single pattern for “source code” (it’s not like a credit card number), but you can train a classifier on a set of known code files. After training, you include that classifier in a DLP policy rule targeting OneDrive and Exchange. If a user tries to share a file that the classifier deems to look like source code, the DLP policy can trigger (warn the user or block it). Meanwhile, simple patterns like API keys or passwords within text can be handled by SITs or regex in the same policy.


DLP Policy Actions and User Override Options

When a DLP policy identifies sensitive information, it can take several types of actions. These actions determine what happens to the content or user’s attempt. The main actions are: Audit (allow and log), Notify (policy tip or email), Block (with or without override), and Encrypt. Here we explain each and how they function, including the ability for users to override certain blocks:

  • Audit Only (No visible action): The policy can be set to allow the activity but log it silently. In this case, if content matches a DLP rule, the user’s action (sending email or sharing file) is not prevented and they might not even know it triggered. However, the incident is recorded in the compliance logs and available in DLP reports for admin review[1]. Admins might use this in a “test” or monitoring mode – for example, run a policy in audit mode first to gauge how often it would trigger, before deciding to enforce stricter actions. Audit mode ensures no disruption to business while still gathering data.
  • Notify (User Notification and/or Admin Alert): DLP can notify the user, the admin, or both when a policy rule is hit:
    • User Notification (Policy Tip): The user sees a policy tip in the app (such as Outlook, OWA, Word, Excel, etc.) warning them of the policy. For example, in Outlook, a yellow bar might appear above the send button: “This email contains sensitive info (Credit Card Number).”[2]. The tip can be informational or include options depending on policy settings (e.g. Report a false positive, Learn More about the policy, or instructions to remove the sensitive data)[2]. Policy tips do not stop the user by themselves; they are just advisory unless combined with a Block action. However, a strong warning often causes users to correct the issue (e.g., remove the credit card number or apply encryption).
    • Admin Notification (Incident Report): The policy can send an incident report email to specified addresses (like IT/security team) whenever it triggers[2]. This email typically contains details of what was detected (e.g., “An email from Alice to external recipient was blocked for containing 3 credit card numbers”) so that compliance officers can follow up. Admin notifications can be configured to trigger on every event or also based on severity or thresholds (for instance, only notify if there were more than 5 instances, or if the data is highly sensitive)[3][3].

    Use cases: Notify-only is useful when you don’t want to outright block content but want to raise awareness. For example, you might simply warn users and notify IT whenever someone shares something that looks like personal data, to educate rather than punish. It’s also essential during policy tuning phase – run the policy in Notify (or test mode with notifications) to gather feedback from users on false positives.

  • Block: This action prevents the content from being shared or sent. If an email triggers a “block” rule, it will not be delivered to the recipient; if a file is in SharePoint/OneDrive, block can mean preventing external sharing or access. The user will typically be informed that the action is blocked by policy. There are two sub-options for blocking:
    • Block with Override: In this mode, the user is blocked initially, but is given the option to override the block with a justification[1]. For example, a policy tip might say “This content is blocked by DLP policy. Override: If this is a legitimate business need, you may override and send the content by providing a justification.” The user might click “Override” and enter a reason (like “Approved by manager for client submission”). The system logs the user’s decision and justification, and then allows the content to go through[1]. This balances security with flexibility – it lets users proceed when absolutely necessary (preventing business workflow stoppage), but creates an audit trail and accountability. Admins can later review these override incidents to see if they were valid or need further policy tuning.

    Example: If a sales person must send a client’s passport copy to an airline (which violates a “no passport externally” policy), they could override with “Passport needed for booking flight, approved by policy X exemption.” This would let the email send, but security knows it happened and why.

    • Block (No Override): This is a strict block with no user override permitted. The content simply is not allowed under any circumstance. The user will get a notification that the action is blocked and they cannot bypass it. For instance, you may decide that any email containing more than 10 credit card numbers is automatically forbidden to send externally, period. In such cases, the policy tip might inform “This message was blocked and cannot be sent as it contains prohibited sensitive information” with no override option. The user must remove the data or contact admin.

    According to Microsoft’s guidance, DLP can show a policy tip explaining the block, and in the override case, capture the user’s justification if they choose to bypass[1]. All block events (with or without override) are logged to the audit log by default[1].

  • Encrypt: For email scenarios, a DLP policy can automatically apply encryption to the message as an action (this uses Microsoft Purview Message Encryption, previously known as Azure RMS). Instead of blocking an outgoing email, you might choose to encrypt the email and attachments so that only the intended recipients (who likely need to authenticate) can read it[8][8]. In the DLP policy configuration, this is often phrased as “Restrict access or encrypt the content in Microsoft 365 locations” – essentially wrapping the content with rights management protection[8]. For example, if an email contains client account numbers, you might allow it to be sent but enforce encryption such that if the email is forwarded or intercepted, unauthorized parties cannot read it.

    Additionally, for documents in SharePoint/OneDrive, and with integration to sensitivity labels, encryption can be applied via sensitivity labeling. However, in many cases the straightforward use is with Exchange email – DLP can trigger the “Encrypt message” action, thereby sending the email via a secure encrypted channel accessible via a web portal by external recipients[8]. Admins will need to have set up or use the default encryption template for this action to function.

  • Quarantine/Restrict Access: In some instances (especially for SharePoint/OneDrive files or Teams chats), DLP can quarantine content or restrict who can access it. For example, if a file stored in OneDrive is found to contain sensitive data, DLP could remove external sharing links or move the file to a secure quarantine location, effectively preventing others from accessing it[1]. In Teams, if a user tries to share sensitive info in a message, DLP can prevent that message from being posted to the recipient (so the sensitive info “doesn’t display” to others)[1]. These are variations of block actions in their respective services (quarantine is effectively a form of block for data at rest).

User Override Configuration: When setting up a DLP rule, if you select a Block action, you will have a checkbox option like “Allow people to override and share content” (wording may vary) which corresponds to Block with Override. If enabled, you usually can also require a business justification note on override and optionally can allow or disallow the user to report a false positive through the override dialog. Override justifications are saved and can be reviewed by admins (via Activity Explorer or DLP reports showing “User Override” events)[1][1]. In highly sensitive policies, you’d leave override off (for absolute blocking). For moderately sensitive ones, enabling override strikes a balance.

From a user-experience perspective, override typically happens through the policy tip UI in Office apps: the user clicks something like “Override” or “Resolve” on the policy tip, enters a justification text in a dialog, and then is allowed to proceed. The policy tip then usually changes state – e.g., turns from a warning into a confirmation that the user chose to override [2]. The message is then sent or file shared, but marked in logs.

Important: We recommend using “Block with Override” for initial deployment of strict policies. It educates users that something is wrong but doesn’t completely stop business; it also gives admins insight into how often users feel a need to override (which might indicate the policy is too strict or needs refinement if it’s frequently overridden). Only move to full “Block without override” for scenarios that are never acceptable or after trust in the policy accuracy is established.

Policy Tip Customisation: You can customise the text of notifications both to users and admins. For instance, the policy tip can say “This file appears to contain confidential data. If you believe you must share it, please provide a reason.” and the admin incident email can include instructions for the recipient on what to do when they get such an alert. Customising helps align with your company’s tone and provide helpful guidance to users rather than generic messages[3][3].


Step-by-Step Guide to Implementing DLP Policies (Email, SharePoint, OneDrive)

Implementing a DLP policy in Microsoft 365 Business Premium involves using the Microsoft Purview Compliance Portal (formerly Security & Compliance Center). Below is a step-by-step walkthrough for creating and effectively deploying a DLP policy, covering configuration for Exchange email, SharePoint, and OneDrive:

Preparation: Ensure you have the appropriate permissions (e.g. Compliance Administrator or Security Administrator role). Go to the Microsoft Purview Compliance portal at https://compliance.microsoft.com and select “Data Loss Prevention” from the left navigation.

Step 1: Start a New DLP Policy

  1. Navigate to Policies: In the DLP section, click on “Policies” and then the “+ Create policy” button[4]. This launches the policy creation wizard.
  2. Choose a Template or Custom: The wizard will first ask you to choose a policy template category (or a custom option). You have two approaches here:
    • To use a pre-built template, pick a category (e.g. “Financial” or “Privacy”) and then select a specific template. For example, under Financial, you might choose “U.S. Financial Data” if you want to protect things like credit card and bank account info[3]. Each template is briefly described in the UI.
    • To create from scratch, choose the “Custom” category and then “Custom (no template)” as the template. (Some UIs also have an explicit “Start from scratch” option.)

    Click Next after selection. (In our example, if we selected U.S. Financial Data, the policy wizard will pre-load some settings for that scenario.)

Step 2: Name and Describe the Policy

  1. Policy Name: Provide a descriptive name for the policy, e.g. “DLP – Financial Data Protection (Email)”. Choose a name that reflects its purpose; this helps when you have multiple policies.
  2. Description: Enter an optional description, e.g. “Blocks or encrypts emails containing financial account numbers sent outside org. Based on U.S. Financial template.” This description is for admin reference.
  3. Click Next.

(Note: Once created, DLP policy names cannot be easily changed, so double-check the name now[4].)

Step 3: Choose Locations to Apply

  1. Select Locations: You will be asked where the policy applies. The available locations include Exchange email, SharePoint sites, OneDrive accounts, Teams chat and channel messages[6]. For Business Premium focusing on email/SP/OD:
    • Toggle Exchange email, SharePoint, and OneDrive to “On” if you want to include them. (Teams chat can be included if needed for chat messages, though the question emphasizes email/SP/OD.)
    • You can scope within locations as well. For instance, you might apply to “All SharePoint sites” or select specific sites if only certain sites should be governed by this policy, but generally “All” is chosen for broad protection.
    • If this policy should only apply to certain users or groups (via Exchange mailboxes or OneDrives), there is an option to include or exclude specific accounts or conditions (administrative units, etc.)[4]. For an initial policy, you might leave it as all users.

    Click Next after selecting locations.

Step 4: Define Policy Conditions (What to Protect)

  1. Choose Information to Protect: If you used a template, at this stage the wizard will show the pre-defined sensitive info types included. For example, the U.S. Financial Data template might list: Credit Card Number, SWIFT Code, ABA Routing Number, etc., with certain thresholds (like 1 instance low count, 10 instances high count)[6][6]. You can usually add or remove sensitive info types here:
    • To add, click “Add an item” and select additional SITs from the catalogue (or even a trainable classifier or keyword dictionary if needed).
    • To remove, click the “X” next to any SIT you don’t want.
    • If building custom without a template, you’ll have an empty list and need to “Add condition” then choose something like “Content contains sensitive information” and then pick the types. The UI will let you search for built-in types (e.g., type “Passport” or “Credit Card” to find those SIT definitions).
    • You can also set the instance count trigger. Templates often define two rules: one for low count and one for high count occurrences of data, which may have different actions (e.g., 1 credit card found = maybe just notify; 10 credit cards = block)[6][6]. Ensure these thresholds align with your tolerance. You may adjust “min count” or confidence level filters here.
  2. Add Conditions or Exceptions: Optionally, refine the conditions:
    • You might add a condition like “Only if the content is shared with people outside my organization” if you want to protect against external leaks but not internally. For example, you would then configure: If content contains Credit Card Number and recipient is outside org, then trigger. In the wizard, this is often presented as “Choose if you want to protect content only when shared outside or also internally”. Select “people outside my organization” if your goal is to prevent external leaks[3].
    • You can also set exceptions. E.g., Exclude content if it’s shared with a particular domain or if a specific internal user sends it. Exceptions might be used sparingly for business needs or trusted parties.
    • If using labels or a classifier, you could add a condition group: e.g., “Content has label Confidential” OR “Content contains these SITs.” The UI supports multiple condition groups with AND/OR logic.

    On the flip side, ensure you’re not over-scoping: if you want to protect both internal and external, leave the default “all sharing” scope.

  3. Click Next once conditions are set. The wizard often shows a summary of “What content to look for” and “When to enforce” at this point – review it.

Step 5: Set Actions (What happens on a match)

  1. **Select Policy *Actions***: Now determine what to do when content matches the conditions. You will typically see options like:
    • Block access or send (with or without override) – often worded as “Restrict content”. E.g., “Block people from sending email” or “Block people from accessing shared files” depending on location.
    • Allow override: a checkbox to allow user to bypass if you want.
    • User notifications (policy tips): an option like “Show policy tip to users and allow them to override” or “Show policy tip to inform users”. It’s recommended to enable policy tips for user awareness[3].
    • Email notifications: an option to send notification emails. This may have sub-settings: notify user (sender), notify an admin or other specific people. You can input a group or email address for incident reports here.
    • Encryption: for email policies, an option “Encrypt the message” might appear (if configured). You may need to select an encryption template (such as “Encrypt with Office 365 Message Encryption”) from a dropdown.
    • Allow forwarding: sometimes for email, a setting to disallow forwarding of the email if it contains the info, or to enforce encryption on forward. (In newer interfaces, disallow forward is part of encryption templates).

    For our example (financial data email policy): we might choose “Block email from being sent outside”. The wizard might then ask “do you want to allow overrides?” – if we say Yes, it means block with override; if No, it’s a strict block. Let’s say we allow override for now (check Allow override). And we check the box “Show policy tip to users” so they get warned[3]. We also set “Notify admins”: Yes, send an alert to our compliance email (we enter an address or choose a role group). We might choose not to encrypt in this policy since we’re blocking outright; but if instead of blocking we wanted encryption, we’d select that action.

    In multi-location policies, actions can sometimes be set per location. The wizard might show sections for “Email actions” vs “SharePoint actions”. For SharePoint/OneDrive, “block” usually translates to “restrict external access” (prevent sharing outside or remove external users) since the content is at rest. Configure each as needed.

    Microsoft’s default templates often pre-fill some actions: for low-count detection maybe just notify, for high-count detection block. Make sure to adjust these if your intent differs. For instance, the U.S. Financial Data template might default to “notify user; allow override” for 1-9 instances and “block; allow override; incident report” for 10+ instances[6]. You can tweak those thresholds or actions.

  2. Customize Notification Messages (optional): There is typically a link “Customize the policy tip and email text”[3]. Click that to edit the wording:
    • For policy tip: you might type something user-friendly: “Policy Alert: This content may contain financial account data. If not intended, please remove it. If you believe sending is necessary for business, you may override with justification.”
    • For admin email: you can include details or instructions. By default it includes basic info like rule name, user, content title. You could add “Please follow up with the user if this was not expected,” etc.
    • You can also decide if the user sees the policy tip in certain contexts (e.g., maybe show it only when they actually violate by clicking send, or show as soon as they type the number – Outlook can do real-time).

    Save those customisations.

  3. Set Incident Reporting and Severity: Many wizards have a section for incident reports/alerts. For instance, “Use this severity level for incidents” (Low/Medium/High) and “Send an alert to admins when a rule is matched”[4][4]. Choose a severity (perhaps High for a finance data breach) so it’s flagged clearly in the dashboard. Ensure the toggle for admin alerts is on, and frequency set to every time (or you can set to once per day etc. if flood concern).
    • If available, set the threshold for alerting. In some cases you can say “alert on every event” vs “after 5 events in 1 hour” – depending on how you want to be notified. For simplicity, we do each event.
  4. Additional options: If configuring email, you might see a specific setting to block external email forwarding of content or to enforce that external recipients must use the encrypted portal[8][3] – adjust if relevant. In SharePoint DLP, you might see an option like “restrict access to content” which essentially removes permissions for external users on a file if a violation is found.

Click Next after setting all actions and notifications.

Step 6: Review and Turn On

  1. Review Settings: The wizard will show a summary of your policy – the locations, conditions, and actions. Carefully review to ensure it matches your intent (e.g., “Apply to: Exchange email (external), Condition: contains Credit Card Number ≥1, Action: Block with Override + notify user & admin” etc.). It’s easy to go back if something is off.
  2. Choose Policy Mode: You will be prompted to choose whether to turn the policy on right away, or test it in simulation mode, or keep it off. The options usually are:
    • Test DLP policy (Simulation): Runs the policy as if active but doesn’t actually enforce the block actions. Instead, it logs what would have happened and can still show policy tips to users (if you choose “test with notifications”). This mode is highly recommended for new policies[3]. It allows you to see if your policy triggers correctly and how often, without disrupting business. You can check the DLP reports during testing to adjust sensitivity (for example, if you see too many false positives).
    • Turn it on right away (Enforce): Makes the policy active and enforcing immediately after you finish. Only do this if you are confident in the configuration and have possibly tested previously.
    • Keep it off for now: Saves the policy in an off state. You can manually turn it on later. This is similar to test mode but without even simulation. You might choose this if you want to create multiple policies first or only enable after a certain date.

    Select Test mode with notifications if available (this will simulate actions but still send out the user tips and admin alerts so you get full insight, without actually blocking content)[3].

  3. Submit: Finish the wizard by clicking Submit or Create. The policy will be created in the state you selected (off, test, or on).
  4. If in Test Mode, run the policy for a period (a week or two) to gather data. Users will see policy tips but will not be blocked (unless the tip itself convinces them to change behavior). Monitor the DLP reports:
    • Go to Activity Explorer in the compliance portal and filter for DLP events; you’ll see entries of what content would have matched.
    • Check the Alerts section to see if any admin notifications came in (they should if configured, even in test mode).
    • Review any user feedback – if users report confusion or false positives via the “Report” button on a policy tip, take note.

    Fine-tune the policy as needed: maybe adjust the sensitive info types (add an exception for something causing false alarms, or raise the threshold count if it’s too sensitive).

  5. Enable Enforcement: Once satisfied, edit the policy (you can change its mode from test to on). If it was in simulation, you can now switch it to “Turn on” (enforcement mode). Alternatively, you could have initially set it to turn on immediately; in that case, just monitor it closely upon rollout. Communicate to users as needed that certain data (like credit cards, etc.) are now being protected by policy.

Step 7: Ongoing Management

  1. User Education: Make sure to inform your users that DLP policies are in effect. For example, send an email or include in security training: “We have deployed policies to protect sensitive data (like credit card numbers, SSNs, etc.). If you try to send such data externally, you may get a warning or block message. This is for our security and compliance.” Include what they should do (e.g., encrypt emails or get approval if they truly need to send).
  2. Monitor Reports Regularly: After deployment, regularly check the DLP Alerts dashboard and Activity Explorer. Verify that the policy is catching intended incidents and not too many unintended ones. DLP monitoring is an ongoing process – you might discover users trying new ways to send data or needing exceptions.
  3. Adjust Policies: Based on real-world usage, adjust your DLP rules. For instance, you might need to add an allowed exception for a specific partner domain (if it’s legitimate to share certain data with a vendor, you can exclude that domain in the policy). Or you might tighten rules if users find loopholes.
  4. Extend to More Areas: If you started with email, consider extending similar protections to SharePoint/OneDrive if not already. The process is similar – a policy can cover multiple locations or you can create separate policies per location if that makes management easier (some admins prefer one combined policy covering all channels for a certain data type; others prefer distinct policies, e.g., one for “Email outbound PII” and another for “SharePoint data at rest PII”).

Illustration – Policy Tip in Action: When configured, the user experience is as follows: Suppose a user tries to send an email with a credit card number to an external recipient. As soon as they enter the 16-digit number and an external address, a policy tip pops up in Outlook warning them (e.g., “This may contain sensitive info: Credit Card Number. Review policy.”)[2]. If the policy is set to block, when they hit send, Outlook will prevent sending and show a message like “Your organization’s policy blocks sending this content” with possibly an Override button. If override is allowed, clicking it prompts the user to type a justification. Upon confirming, the email is sent, and the user’s action is logged (the email might be encrypted automatically if that was configured). Both the user and admin receive notification emails about this incident (user gets “You sent sensitive info and it was allowed due to your override” and admin gets an alert detailing what happened)[3]. If override was not allowed, the user simply cannot send until they remove the sensitive content.

Illustration – SharePoint/OneDrive: If a file containing sensitive data is uploaded to OneDrive and the user attempts to share it with an external user, a similar policy tip might appear in the sharing dialog or they may get an email notification. The sharing can be blocked – the external person will not be able to access the file. The user might see a message in the OneDrive interface like “Sharing link removed – A data loss prevention policy has been applied to this content” (in modern UI). The admin would see an incident logged for this file. The user could have the option to override if enabled (possibly via a checkbox like “I understand the risks, share anyway”).

Following these steps ensures you implement DLP systematically and with caution (using test mode to avoid disruption). Screenshots from the Compliance Center wizard and Outlook policy tips can be found in Microsoft’s documentation for reference[3][3], which visually guide where to click and what messages appear.


Real-World Scenarios and Best Practices

Real-World Scenarios: DLP policies in M365 Business Premium can address a variety of common business needs. Here are a few scenarios illustrating effective use:

  • Scenario 1: Protecting Credit Card and Personal Data in Emails – A retail company wants to ensure employees don’t send customers’ credit card details or personal IDs via email to external addresses. They use the built-in Financial data template to create a policy for Exchange Online. If an email contains a credit card number or social security number and is addressed outside the company, the user is warned and the email is blocked unless they override with a valid business reason. This prevents accidental leakage of PCI or PII data via email[3][3]. Over time, the number of such attempts drops as employees become aware of the policy.
  • Scenario 2: Securing Confidential Files in SharePoint/OneDrive – A consulting firm stores client data on SharePoint Online. They implement a DLP policy to detect documents containing phrases like “Project Classified” and client account numbers (using custom SIT for account IDs). The policy applies to SharePoint and OneDrive, and blocks sharing of such documents with anyone outside their domain. A consultant who attempts to share a marked confidential document with a client’s Gmail address gets a notification and the action is prevented. An override is not allowed due to the sensitivity. The admin receives an alert to follow up. This ensures that confidential deliverables aren’t accidentally shared beyond intended channels.
  • Scenario 3: Compliance with Health Data Regulations (HIPAA) – A healthcare provider uses a DLP policy based on the HIPAA template to guard ePHI (electronic protected health info). The policy looks for medical record numbers, patient IDs, or health insurance claims numbers in both emails and OneDrive. If a nurse tries to email a patient’s record externally or save it to a personal cloud, the system flags it. In this case, the policy is set to encrypt any outbound email containing patient health info rather than block (since doctors may need to send info to outside specialists). So the email is delivered but only accessible via a secure encrypted message portal[3]. This meets HIPAA requirements by protecting data in transit, while still permitting necessary flow of information in patient care.
  • Scenario 4: Intellectual Property (IP) Protection – An engineering firm wants to prevent design documents or source code from leaking. They train a classifier on sample source code files. They also define a custom keyword list for project code names. A DLP policy combines these: if a document matches the “Source Code” classifier or contains project code names and is shared externally, it’s blocked. For email, they additionally use a policy tip allowing override with justification (so if a developer legitimately needs to send code to a vendor, they can, but it’s tracked). This multi-pronged approach catches anything that looks like code or proprietary project info leaving the company, safeguarding intellectual property.
  • Scenario 5: Data Privacy (GDPR Personal Data) – A multinational company subject to GDPR defines a policy to detect personal data (SITs like EU National ID, passport numbers, IBANs, etc.). They apply it to all locations – if personal data is being sent to external recipients or shared publicly, the user gets a warning. The policy is initially in audit/notify mode to measure incidents. They find many hits in OneDrive where employees back up contact lists that include customer info. Using reports, they educate those users and adjust the policy. Eventually they enforce blocking for certain info like national IDs, while allowing override for less sensitive fields. This helps build a culture of privacy by design, as users start thinking twice before sharing files with lots of personal data.

Best Practices for Effective DLP:

  • Start in “Shadow Mode” (Testing): When introducing a new DLP policy, begin with it in Test/Monitoring mode (no blocking) or with only notifications. This lets you see how often it triggers and whether there are false positives, without disrupting business[3]. Use the test results to fine-tune conditions (e.g., add an exception if a certain internal process constantly triggers the policy benignly). Once refined, switch to enforce mode. This phased approach prevents chaos on day one of DLP enforcement.
  • Use Policy Tips to Educate Users: Policy tips are a powerful way to make DLP a collaborative effort with employees. Ensure policy tips are enabled wherever appropriate, and craft clear, friendly tip messages. For example, instead of a cryptic “DLP rule 4 violated,” say “Warning: This file contains SSNs which are not allowed to be shared externally. Please remove them or use encryption.” This helps users learn the policies and the reasons behind them, turning them into allies in protecting data[2]. Additionally, encourage users to utilize the “Report False Positive” option if they believe the policy misfired – this feedback loop can help you improve accuracy.
  • Leverage Pre-Built SITs and Templates: Microsoft’s built-in sensitive info types and templates cover a wide range of common needs. Avoid reinventing the wheel – use them as much as possible. Only create custom SITs or rules if you truly have to. The built-ins have undergone refinement (for example, the Credit Card Number SIT will avoid false hits by requiring checksum validation and keywords)[2]. Utilizing these saves time and usually yields reliable detection out-of-the-box.
  • Combine Multiple Conditions Carefully: If you have multiple sensitive info types you want to protect in one policy, consider whether they should be in one rule or separate rules. One rule can contain multiple SITs but then the same actions apply to all if any trigger[9][9]. If you need different handling (e.g., maybe block credit cards but only warn on phone numbers), those should be separate rules (or even separate policies). Also use the condition logic (AND/OR) thoughtfully:
    • Use AND if you want a rule to trigger only when multiple criteria are met together (e.g., document has Project code AND marked Confidential).
    • Use OR (separate rules) if any one of multiple criteria should trigger (most common case).
    • Use exceptions rather than overloading too many NOT conditions in the rule; it’s clearer to manage.
  • Define Clear Policy Scope: Align DLP policies with business processes. For instance, if only Finance department deals with bank accounts, you might scope a bank account DLP rule just to Finance’s OneDrive and mail, to avoid impacting others unnecessarily. Conversely, a company-wide policy for customer PII might apply to all users. Metadata-based scoping (such as using Teams or SharePoint site labels, or targeting certain user groups) can improve relevance.
  • Set Incident Response Workflow: Ensure that when DLP incidents occur (especially blocks), there is a process to address them. Assign personnel to check DLP alerts daily or have alerts go into a ticketing system. If a user repeatedly triggers DLP or overrides frequently, it might require an educational email or management review. DLP is not “set and forget” – treat it as part of your security operations. Over time, analyze incident trends: which policies fire the most, are they real risks or nuisance triggers? Use that insight to update training or adjust DLP logic.
  • Tune for False Positives and Negatives: No DLP is perfect initially. Be on the lookout for false positives (innocuous content flagged) and false negatives (sensitive content getting through). False positives common examples: a 16-digit tracking number being mistaken for a credit card, or a random number that fits the pattern of a national ID. To reduce false positives, you can raise the count threshold, add validating keywords, or adjust confidence level required (e.g., require “High confidence” matches only)[3]. For false negatives, consider if the SIT pattern needs expansion or if users are finding ways around detection (like writing “1234 5678 9012 3456” with spaces – though MS SITs often catch that. If not, you may broaden the regex). It’s a continual tuning process.
  • Keep DLP Policies Updated: Revisit your DLP configurations regularly (e.g., quarterly)[5]. As business evolves, new sensitive data types might emerge (e.g., you start collecting biometric IDs), or regulations change. Microsoft also updates the service with new features and SITs – review release notes (e.g., new SITs or classifier improvements) to take advantage. Also, if you notice a policy hasn’t logged any events in months, verify if it’s still needed or if perhaps it’s misconfigured.
  • Use Simulation for Impact Analysis: If you plan to tighten a policy (like moving from override -> full block, or adding a new sensitive info type to an existing policy), consider switching it back to Test Mode for a short period with the new settings. This gives you data on how the change would play out. Especially for big scope changes (like applying a policy company-wide rather than to one department), simulation can prevent unintended business halts.
  • Combine DLP with Sensitivity Labels: A best practice is to use Sensitivity Labels (from Microsoft Information Protection) to classify highly sensitive documents, and then have DLP rules that reference those labels. For example, label all documents containing trade secrets as “Highly Confidential” (either manually by users or via auto-labeling), then a DLP policy can simply have a condition “If document has label = Highly Confidential and is shared externally, block it.” This approach can be more accurate since labeling incorporates user knowledge and additional context beyond pattern matching. It also means DLP isn’t re-evaluating content from scratch if a label is already applied.
  • Monitor User Feedback & Adapt: Pay attention to how users interact with DLP. If they are frequently overriding a particular policy with “false positive” justifications, that indicates a need to adjust that policy or train users better. Conversely, if users never override and always comply, you might try tightening the policy further or maybe you could safely enforce encryption instead of just warning.

By following these best practices, you’ll implement DLP controls that effectively protect data without unduly hampering productivity. A well-tuned DLP system actually becomes almost invisible – catching only genuine policy violations and letting normal work flow uninterrupted – which is the end goal.


Potential Pitfalls and Troubleshooting Tips

Even with careful planning, you may encounter some challenges when deploying DLP in Microsoft 365. Below we list common pitfalls and how to troubleshoot or avoid them:

Common Pitfalls / Challenges
  • Overly Broad Policies (False Positives): A policy that’s too general can trigger on benign content. For example, a policy that flags any 9-digit number as a SSN could halt emails with order numbers or random data that coincidentally have 9 digits. This can frustrate users and lead them to ignore or work around DLP alerts. Best Avoided By: refining your patterns (use built-in SITs with verification, or add context requirements). Also consider using higher instance counts for triggers – e.g., a single credit card number might be legitimate (a customer providing their payment info), but multiple cards likely isn’t; the template addresses this by separate rules for count =1 vs many[6][6]. Leverage that design to reduce noise.
  • Too Many Exceptions (False Negatives): The opposite – if you exempt too many conditions to reduce noise, you might inadvertently let sensitive data slip. For instance, excluding all internal emails from DLP might miss a scenario where an insider mistakenly emails a file to a personal Gmail thinking it’s internal. Mitigation: Try using “outside my organization” condition instead of broad exceptions, and be cautious with whitelisting domains or users. Ensure exceptions are narrow and justified. Periodically audit the exceptions list to see if they’re still needed.
  • User Workarounds: If users find DLP blocks onerous, they might attempt to circumvent them, e.g., by splitting a number across two messages or using code words for data. While DLP can’t catch everything (especially deliberate misuse), it’s a sign your policy may be too restrictive or not communicated well. Mitigation: Gather feedback from users. If they resort to workarounds to accomplish necessary tasks, consider adjusting the policy to allow those via override (so at least it’s tracked). Also, carry out user training emphasizing that bypassing DLP policies can be a policy violation itself, and encourage using the provided override with justification instead of sneaky methods. DLP is there to protect them and the company, not just to block work.
  • Performance and Client Compatibility: Policy tips appear in supported clients (Outlook desktop 2013+, OWA, Office apps). In unsupported clients (or if offline), the block may still occur server-side but the user experience might be confusing. Also, DLP only scans the first few MBs of content for tips (for efficiency) – so extremely large files might not trigger a tip even if they contain an ID at the very end, though the server will catch it on send. Mitigation: Educate users on which clients support real-time tips (e.g., Outlook on the web and latest Outlook desktop do; older mobile apps might not). Also, if you have very large files, consider splitting them or note that DLP might not scan everything for tip purposes (though it will for actual enforcement).
  • Endpoint and Offline Gaps: Business Premium’s DLP does not cover endpoints (unless you have add-ons) the same way as cloud. That means if a user has sensitive data and tries to copy it to a USB drive or print it, the default M365 DLP won’t stop that – those are endpoint DLP features available in E5. Users might exploit this gap. Mitigation: Use other measures like BitLocker for USB, device management, and educate employees that copying sensitive files to unauthorized devices is against policy. Microsoft provides an upgrade path to Endpoint DLP if needed, but in absence, focus on cloud channels which are covered.
  • Ignoring Alerts: If the security team doesn’t actively review DLP alerts and logs, incidents might go unnoticed. DLP isn’t “blocking everything” – some policies might be notify-only by design. If those notifications aren’t read by someone, the benefit is lost. Mitigation: Set up a clear alert handling process. Even if you have alerts emailed, consider also having a Power Automate or SIEM rule that collects DLP events for analysis. Regularly check the Compliance Center’s Alerts. If volume is high, use filters or thresholds to prioritize (the DLP alert dashboard can highlight highest severity issues).
  • Policy Conflicts: If you create multiple DLP policies that overlap (e.g., two policies apply to the same content with different actions), it can be unclear which one wins. Generally, the more restrictive action should win – e.g., if one policy says block and another says allow with notification, the content will be blocked. But it can confuse troubleshooting when an incident shows up under a certain policy. Mitigation: Try to structure policies to minimize overlaps. Perhaps have one global policy per category of data. If overlaps are needed, document the hierarchy (you might rely on Microsoft’s default priority or adjust the order if the portal allows).
  • Data Not Being Detected: Sometimes you might find that clearly sensitive data wasn’t caught by DLP. Possible reasons include:
    • The data format didn’t match the SIT’s pattern (e.g., someone wrote a credit card like “4111-1111-1111-1111” with unusual separators and maybe the SIT expected no dashes – though the built-in usually handles common variations).
    • The content was embedded in an image or scanned document – OCR is not performed by DLP by default, so an image of a document with SSNs would not trigger.
    • The policy location wasn’t correctly configured (maybe OneDrive for that user wasn’t included, etc.).
    • The policy was in test mode (logging only) and you expected a block.

    Troubleshooting: Double-check the Content: test the specific content against the SIT’s detection logic (Microsoft’s compliance portal has a “Content explorer” and SIT testing tool). For images, consider using Azure Information Protection scanner or trainable classifier if needed (outside scope of basic DLP). Verify the Policy settings: is that user or site excluded? Is it running in simulation only? Use the DLP incident details in Activity Explorer – it often shows which rule did or didn’t fire and why. If needed, adjust the regex or add that specific string as a keyword to pick it up. For advanced needs like OCR, you may need supplementary tools.

Troubleshooting Tips
  • Use the DLP Test Feature: Microsoft provides a way to test how content is evaluated by DLP. In the Compliance Center’s Content Explorer or policy setup, you might find options to test a string against an SIT. There are also PowerShell cmdlets (like Test-DlpPolicy in Exchange Online) that can simulate a DLP policy against given content to see if it would match. This is useful for troubleshooting a rule – e.g., “Why didn’t this trigger?” or “Is my custom regex working?”[1].
  • Policy Tips Troubleshooter: If policy tips are not showing up where expected (say in Outlook), Microsoft has a diagnostic and guidance. Common issues: the user’s Outlook might not be in cache mode, or the mail flow rule side of DLP took precedence without the client seeing it. Ensure the DLP policy actually has user notifications enabled, and that the client application is up to date. Try the same scenario in OWA vs Outlook to isolate client-side issues.
  • Check the Audit Log: All DLP actions (whether just a tip shown, an override done, or a block) are recorded in the unified audit log. If something odd happens, go to Audit > Search and filter by activities like “DLP rule matched” or “DLP rule overridden”. You can often trace exactly what rule acted on a message and what the outcome was. For instance, if a user claims “I wasn’t able to override”, the audit might show they attempted and perhaps they didn’t meet a condition or the policy disallowed it. The log entry will also show which policy GUID triggered – you can confirm if the correct policy fired.
  • Simulate Different License Levels: If certain features (like trainable classifiers or some SITs) aren’t working, it could be a licensing limitation. Business Premium includes most DLP for cloud but not some extras. The interface might still show options (like Device/Endpoint location or advanced classifiers) but they might not function fully. If you suspect this, consult the documentation on licensing to see if that capability is supported[5]. In some cases, a 90-day E5 compliance trial can be activated to test advanced features in your tenant[1].
  • Use Microsoft Documentation and Community: Microsoft’s official docs (Purview DLP section) have detailed policy reference and troubleshooting guides. If something is puzzling (like “Emails with exactly 16 digits are always flagged even if not a credit card”), the docs often explain the rationale (maybe a regex pattern or included keyword). They also list all built-in SITs and definitions, which is helpful for troubleshooting patterns. The Microsoft Tech Community forums and blogs are full of Q&A – chances are someone encountered a similar issue (for example, false positives with certain formats) and solutions are posted. Don’t hesitate to search those resources.
  • Incremental Rollout: If troubleshooting a really large-scale policy, try applying it to a small pilot group first. For example, scope the policy to just IT department mailboxes for a week. This way, if it misbehaves, impact is limited, and you can gather debug info more easily. Once it’s stable, widen the scope.
  • Troubleshoot User Overrides: If you allowed overrides but never see any in logs, it might be that users aren’t noticing they have the option. Ensure the policy tip explicitly tells them they can override if they click a certain link. If overrides are happening but you want to ensure they had proper justification, note that justification texts are recorded – review the incidents; if they left it blank (some older versions didn’t force text), consider requiring it or educating users to fill it in.
  • Pitfall: Assuming 100% Prevention: Finally, know the limits – DLP significantly reduces risk but no DLP can guarantee all forms of data loss are stopped. Users can always find ways (e.g., use personal devices to take photos of data, or encrypt data before sending so DLP can’t see it). DLP should be one layer of defense. Combine it with user training, strong access controls, and possibly other tools (like Cloud App Security for shadow IT, etc.) for a more holistic data protection strategy. Set management’s expectation that DLP will catch the common accidental leaks and policy violations, but it’s not magic – vigilant security culture is still needed.

References and Further Reading

For more detailed information and official guidance, consider these Microsoft resources (which were referenced in compiling this guide):

  • Microsoft Learn – Overview of DLP: Learn about data loss prevention[1][1] – an introduction to how DLP works across Microsoft 365, including definitions of policies, locations, and actions.
  • Microsoft Learn – DLP Policy Templates: What the DLP policy templates include[6][6] – documentation listing all the out-of-box templates, their included sensitive info types and default rules (useful for deciding which template to start with).
  • Microsoft Learn – Create and Deploy a DLP Policy: A step-by-step guide in Microsoft’s documentation for configuring DLP policies, with scenario examples[4][4].
  • Tech Community Blog – DLP Step by Step: “Data Loss Prevention Policies [Step by Step Guide]” by a community contributor[9][9] – explains in simple terms the structure of DLP policies (policy > rules > SITs) and provides a walkthrough with screenshots of the process (from 2022 but principles remain similar).
  • Microsoft Purview Trainable Classifiers: Get started with trainable classifiers[7][7] – for learning how to create and use trainable classifiers if your DLP needs go beyond built-in patterns.
  • Official Microsoft Documentation – Policy Tips and Reports: Articles on customizing and troubleshooting policy tips[2][3], and using the Activity Explorer & alerting dashboard to monitor DLP events[1][1].
  • Microsoft 365 Community & FAQs: There are numerous Q&A posts and best-practice nuggets on the Microsoft Community and TechCommunity forums. For example, handling false positives for credit card detection, or guidance on using DLP for GDPR.

By following the guidance in this report and diving into the resources above for specific needs, you can implement DLP policies in Microsoft 365 Business Premium that effectively protect your organisation’s sensitive data across email, SharePoint, and OneDrive. Remember to phase your rollout, educate your users, and continuously refine the policies for optimal results. With DLP in place, you build a safer digital workplace where accidental data leaks are minimized and compliance requirements are met confidently. [5][5]

References

[1] Learn about data loss prevention | Microsoft Learn

[2] Office 365 compliance controls: Data Loss Prevention

[3] Configuring data loss prevention for email from the … – 4sysops

[4] Create and deploy a data loss prevention policy | Microsoft Learn

[5] How to Setup Microsoft 365 Data Loss Prevention: A Comprehensive Guide

[6] What DLP policy templates include | Microsoft Learn

[7] Get started with trainable classifiers | Microsoft Learn

[8] Data loss prevention Exchange conditions and actions reference

[9] Data Loss Prevention Policies [STEP BY STEP GUIDE] | Microsoft …

Securing Microsoft Edge Browser with M365 Business Premium: Best Practices & Deployment Guide

bp1

Microsoft Edge is a modern, secure-by-default browser, but organizations can further harden it using tools in Microsoft 365 Business Premium – especially Microsoft Intune – to protect users and data. This post outlines best practice security settings for Microsoft Edge and details how to deploy and manage these settings across a fleet of devices using Intune. We also cover ongoing management, monitoring, and user awareness to ensure maximum day-to-day protection.


Introduction: Why Secure Edge with Intune

Microsoft Edge for Business provides a dedicated work browser experience that is secure by default, separating work and personal browsing data to prevent leaks[6]. It includes robust built-in security features (like Microsoft Defender SmartScreen) and supports enterprise controls. However, to achieve a consistent security posture across all devices, IT administrators should enforce configurations via Intune. Microsoft Intune (part of M365 Business Premium) allows centralized management of Edge’s security settings on Windows PCs, Macs, and mobile devices. By leveraging Intune policies, security baselines, and integration with other Microsoft 365 security tools, organizations can:

  • Enforce security best practices on every Edge browser used for work (e.g. enable phishing protection, restrict unsafe features).
  • Deploy these settings at scale to all managed endpoints (Windows, macOS, mobile) in a uniform way.
  • Ensure compliance with organizational security requirements and industry recommendations.
  • Monitor and update Edge configurations over time, responding to new threats and updates.

In the sections below, we’ll first explore the key Edge browser security settings and best practices. Then we’ll provide a step-by-step guide to implement these via Intune, discuss deployment to multiple devices, and cover management, updates, and user training.


Best Practice Security Settings for Microsoft Edge

To secure Edge browsers in an enterprise environment, administrators should focus on several critical security areas. Microsoft provides an Edge security baseline – a template of recommended settings – which we will use as a reference for best practices. This baseline reflects the latest security team recommendations for Edge’s configuration[1]. Below is a summary of key Edge security settings and their recommended state (as per Microsoft’s baseline and industry best practices), along with their purpose:

Security Setting Recommended Configuration Purpose / Protection
Microsoft Defender SmartScreen Enabled (On) Blocks access to phishing sites, malicious downloads, and other threats in real-time.
SmartScreen – Potentially Unwanted Apps (PUA) Enabled (On) Blocks download of adware, browser hijackers, and other low-reputation apps.
SmartScreen Bypass Disallow user bypass Prevents users from clicking through warning pages for malicious sites or files.
Typosquatting Checker Enabled Warns users if they mistype URLs and helps avoid look-alike malicious sites.
Site Isolation (Strict Site Per Process) Enabled (On) Isolates each website in its own process, mitigating spectre-type attacks between sites.
Legacy Browser Mode (IE mode) Disabled unless needed Avoids using Internet Explorer mode except for approved legacy sites, reducing exposure to older insecure web technologies.
HTTP/Legacy Authentication Disable Basic auth Blocks legacy HTTP Basic authentication to prevent sending credentials in cleartext; only allow modern auth (NTLM/Kerberos).
Browser Extensions Restrict add-ons (block unapproved) Block all unauthorized extensions – by default, no extensions are allowed unless whitelisted. This prevents installation of malicious or unvetted add-ons which could hijack the browser.
Legacy Extension Points Enabled (Block legacy hooks) Blocks old-style extension injection points, preventing malware from using unsupported methods to hook into Edge.
Application Bound Encryption Enabled Encrypts browser data tied to user identity or device, adding a layer of protection for stored credentials/cookies.
Insecure Network Requests Blocked Blocks requests from HTTP websites to local or more secure network resources (protects against cross-network attack vectors).
TLS/Encryption Protocols Enforce TLS 1.2+ Ensure only modern TLS versions (1.2 or 1.3) are used, preventing fallback to deprecated 1.0/1.1 protocols that have known weaknesses.
Password Manager / Autofill Configured securely Consider disabling password save for sensitive accounts or ensure saved passwords are protected by OS credentials. (The baseline doesn’t disable it entirely, but organizations may choose to manage this depending on policy.)
Automatic Updates Enabled (Auto-update Edge) Allow Edge to update itself automatically on all devices for timely security patches. Do not disable the built-in update mechanism.

As shown above, Microsoft’s Edge security baseline already sets most of these configurations to the recommended values by default.[1] By using this baseline (or configuring equivalent settings manually), you achieve a hardened browser configuration that significantly reduces risk.

Below we further explain some of these best practices and why they are important:

  • SmartScreen & Phishing Protection:
    Microsoft Defender SmartScreen is a cloud-based URL and app reputation service built into Edge. Enabling SmartScreen (with no user bypass) is critical – it provides industry-leading protection against phishing websites, malicious drive-by downloads, and other web threats
    [2][1]. SmartScreen will block known dangerous sites and files, and with Potentially Unwanted App blocking enabled, Edge also prevents users from inadvertently downloading unwanted software like adware[1]. The baseline sets SmartScreen and PUA blocking on, and even stops users from bypassing the warnings[1], ensuring maximum protection.
  • Typosquatting Checker:
    This feature warns users if they mistype a popular URL (for example, “micros0ft.com” instead of “microsoft.com”) and might have landed on a fraudulent look-alike site. Enabling typo protection helps prevent credential theft via spoofed domains
    [2]. The Edge security baseline enables this by default[1].
  • Site Isolation:
    Site Isolation (also known as strict site-per-process) forces each website to run in a separate browser process. This is a defense against attacks like Spectre, which attempt to read data across sites via speculative execution vulnerabilities. With site isolation enabled, a malicious site cannot easily access data from other sites’ sessions
    [7][3]. Microsoft’s baseline now enables full site isolation for every site (earlier versions had it off, but it’s enabled in newer baseline versions)[3].
  • Legacy Content (Internet Explorer Mode):
    Edge can use IE mode for legacy web apps, but IE’s outdated rendering can pose security risks. Best practice is to minimize the use of IE mode. The baseline disables loading unconfigured sites in IE mode
    [1] and hides the “Reload in IE mode” button[1], so IE is only used for sites explicitly configured by IT. This reduces exposure to old ActiveX or insecure controls. Only enable IE mode for trusted internal sites that absolutely require it.
  • Encryption and Network Protections:
    Edge and Windows support modern encryption protocols. Force strong encryption by disallowing legacy protocols. The baseline, for instance, disables old TLS 1.0/1.1 (Edge already deprecated these by default) and ensures TLS 1.2 is the minimum
    [7]. It also disables HTTP Basic authentication in the browser[1] – Basic auth sends credentials in plaintext and should be avoided in favor of NTLM or OAuth flows[1]. Additionally, Edge baseline disables insecure cross-network requests (Private Network Access)[1], which stops public websites from reaching into internal resources by default – mitigating certain CSRF and lateral movement scenarios.
  • Extensions Management:
    Browser extensions can greatly increase productivity but also introduce risk. Malicious or poorly made extensions might redirect users to phishing sites, inject ads or scripts, or steal data
    [7]. A best practice is to allow only approved extensions. The Intune Edge baseline helps here by including a setting to block all extensions by default[1]. Administrators can then maintain an allow-list of specific extensions if needed (by specifying permitted extension IDs and leaving others blocked). This way, users can’t install random add-ons – reducing malware and data leak risks. If your organization needs certain extensions (password managers, etc.), explicitly approve those and keep the list minimal and reviewed.
  • Legacy Plug-ins and Code:
    Edge has a setting to block legacy extension points (legacy plug-in APIs or injection mechanisms used by older apps/malware). The baseline keeps this blocking enabled
    [1] to prevent any unsupported mechanism from loading into Edge’s process. This hardening measure protects against malware that tries to use outdated hooks to compromise the browser.
  • Application Bound Encryption:
    Newer versions of Edge support Application Bound Encryption, which ties data encryption to the application context or user’s corporate identity. The security baseline enables this by default
    [1]. In effect, it ensures certain sensitive data that Edge stores (like cookies or credentials) are additionally encrypted such that only Edge (or only the user’s profile) can use them. This reduces the risk of sensitive browser data being stolen and used outside the browser, even if the underlying OS is compromised.
  • Auto-Updates for Edge:
    Keeping Edge up-to-date is one of the simplest yet most vital security practices. Microsoft Edge receives frequent security updates (aligned with a 4-week stable channel cycle). Allow Edge to update automatically in your environment. By default, Edge’s internal updater will periodically check and install updates
    [5]. Intune can enforce the update check frequency if needed (via Edge Update policies)[5], but generally the key is: do not disable or delay Edge updates. Ensuring all users run the latest Edge version means known browser vulnerabilities are patched and the latest protections are active. We will discuss later how Intune can help monitor or enforce update compliance.

By implementing the above settings, you establish a strong defensive baseline for web browsing. Next, we’ll describe how to use Intune to configure these settings across all your devices in a scalable way.


Implementing Edge Security Policies with Intune

Microsoft Intune (part of the Endpoint Manager) is the primary tool to enforce the Edge configurations described. Intune offers multiple methods to deploy browser policies:

  1. Security Baselines – Microsoft provides a pre-packaged Microsoft Edge Security Baseline profile in Intune. This is a template with a comprehensive set of recommended settings (many of which we summarized above) that you can deploy with minimal effort. The baseline ensures a default secure posture for Edge aligned with Microsoft security team guidance[1].
  2. Configuration Profiles – For more granular control or to implement settings not in the baseline, Intune allows custom Configuration Profiles. Using the Settings Catalog or Administrative Templates in Intune, admins can configure individual Edge policies (analogous to Group Policy settings) and deploy them. This can supplement or fine-tune the baseline.

We’ll focus first on using the Edge Security Baseline, as it covers best practices out-of-the-box.

Using the Microsoft Edge Security Baseline in Intune

Intune’s Security Baseline for Edge is the fastest way to apply a broad set of hardened settings to Edge browsers. It includes dozens of configurations with Microsoft’s recommended defaults. Follow these steps to create and deploy an Edge baseline profile:

  1. Open Endpoint Security > Security Baselines in Intune: Sign in to the https://endpoint.microsoft.com/ and navigate to Endpoint security > Security baselines. You’ll see a list of available baseline templates (Windows 10, Defender for Endpoint, Microsoft Edge, etc.)[3].
  2. Select the Edge baseline and create a profile: Choose Microsoft Edge (version 112 and later) from the list (this is the Edge for Windows 10/11 baseline)[3]. Click + Create profile. Give the profile a name (e.g. “Edge Browser Security Baseline”) and optional description[3].
  3. Review and configure settings: On creation, you can review the baseline’s settings groups. By default, all settings are set to Microsoft’s recommended value (as summarized in the table above). You can leave them as-is for a standard deployment. Optionally, you may customize specific settings – for example, if you want to allow a particular extension or adjust a policy, you can modify that before deployment. Intune’s interface lets you expand categories (Security, Privacy, Extensions, etc.) and see each setting and its default[3]. Insights (lightbulb icons) may be available next to settings to indicate how many other organizations enable a setting, which can guide you[3].
  4. Assign the baseline profile to device groups: Once the profile is ready, proceed to the Assignments step. Select one or more Azure AD groups containing the target users or devices to include[3]. For example, you might assign it to an “All Corporate Devices” group. (You can also exclude certain groups if necessary, e.g., a pilot or IT testing group.) Note: The Edge baseline contains both computer and user settings, and Intune will handle applying them appropriately. At least one group must be assigned, otherwise the profile won’t deploy[3].
  5. Finish and deploy: Click Review + create and then Create. As soon as you create the baseline profile, Intune will push it to all devices in the assigned groups[3]. Managed PCs will receive the settings policy over the air. Users might need to restart Edge for certain policies to take effect immediately, but many settings apply dynamically.

Tip: It’s recommended to test new baselines on a small set of devices before broad deployment. Intune allows creating multiple baseline profiles – you could assign a baseline first to a pilot group, verify the impact, then roll out to everyone[3]. You can also duplicate a baseline profile and update it (e.g., when a new baseline version is released) for testing before replacing the old one[3].

  1. Monitor deployment status: After deployment, you can check Intune > Endpoint security > Security baselines > [Your Edge baseline] > Device status to see a report of devices and whether the policy succeeded, is pending, or has errors. A successful status indicates the device has applied the Edge settings. We’ll cover more on monitoring in a later section.

Using the security baseline is often the best method, as it bundles all essential settings. However, you might want to adjust or add policies outside the baseline. For instance, maybe you want to configure a new Edge setting that the current baseline doesn’t include, or you want a slightly different value for a particular setting. This is where custom configuration profiles come in.

Custom Edge Configuration via Settings Catalog (Optional)

Intune’s Settings Catalog provides access to all available Edge policies (equivalent to the Chrome/Edge ADMX settings) that you can configure in a profile. This approach is useful if you need to:

  • Add settings beyond what the baseline covers (for example, a brand-new Edge feature or a less common setting).
  • Relax or tighten a baseline setting for specific groups (e.g., allow a certain extension for developers while baseline blocks all others).
  • Manage Edge settings on platforms like macOS (the Windows baseline might not apply there, so you’d create a separate macOS configuration profile for Edge).

To create a custom Edge policy profile:

  1. In the Intune admin center, go to Devices > Configuration profiles and create a new profile. Choose the appropriate platform (Windows 10/11, macOS, etc.) and pick Settings Catalog as the profile type.
  2. Under Configuration settings, click Add settings. Search for “Edge” to see categories of Edge browser settings. Intune lists hundreds of available settings derived from the Edge administrative template.
  3. Select the desired settings and set their values. For example, to enforce extension blocking manually: find “Control which extensions cannot be installed” and add it, then set it to Enabled and specify “*” (block all) as the prohibited extensions list[1]. Likewise, you can configure SmartScreen (Enable Microsoft Defender SmartScreen = Enabled)[1], “Prevent bypass of SmartScreen warnings” (Enabled)[1], “Enable site isolation” (Enabled) etc., matching the best practices discussed. Each setting in the catalog includes a description of what it does, and often a link to documentation.
  4. Once you’ve configured all needed settings, assign the profile to your device/user groups similar to the baseline assignment. Intune will deploy these settings to those devices.
  5. Monitor the profile deployment under the profile’s Device status, and resolve any conflicts. (If a device has both a baseline and a custom profile with overlapping settings, ensure they are consistent. Intune will mark a conflict if two policies set the same setting differently. It’s usually best to avoid duplicates – you can stick mostly to baseline OR custom for a particular setting, but not both with different values.)

Using the Settings Catalog approach requires more manual work to select and configure each setting, but it provides flexibility. Many organizations will start with the Edge security baseline (for broad coverage) and layer any additional needed settings via a small custom profile.

Intune App Protection (MAM) for Edge on Mobile

In addition to device configuration profiles (which apply to managed devices), M365 Business Premium allows App Protection Policies for scenarios where you manage only the app (Edge) on a mobile device. For example, if employees access corporate web apps via Edge on their personal phone (without enrolling the phone in Intune), you can use Intune’s MAM (Mobile Application Management) policies on Edge for iOS/Android.

These policies can require a PIN to open the app, prevent data from Edge being copied to personal apps, require Edge to open links from corporate emails, etc. Edge for Business on mobile can be managed such that corporate data viewed in the browser is containerized and protected[6]. If this scenario applies, configure an App Protection Policy targeting the Edge app for your user group – enabling features like app-level encryption, disable “Save-as” for files, block screenshots, and so on, to secure corporate web access on unmanaged devices[6]. This extends your Edge security to BYOD cases.


Deploying Policies Across Your Device Fleet

Deploying the Edge security settings across a fleet is straightforward with Intune once the profiles (baseline or custom) are set up. Here are some best practices for fleet-wide deployment:

  • Organize devices into Azure AD groups: Intune assignments are group-based. Ensure all company endpoints are members of a group (or multiple groups) that you target with the Edge policy. Many admins use an “All Managed Devices” dynamic group. Alternatively, separate groups by platform if you have different profiles for Windows vs. macOS.
  • Include new devices automatically: If using dynamic device groups (e.g., all devices with a specific enrollment tag or all Windows 10 devices), any new device enrolled into Intune will automatically receive the Edge policies shortly after enrollment. This is useful for autopilot scenarios – when a new PC is set up, it joins Intune and moments later the Edge hardening policy is applied, ensuring compliance from day one.
  • User vs Device targeting: The Edge baseline can be assigned to device groups (then user settings in it apply to any user on those devices) or to user groups (then when that user logs into any managed device, the settings apply). Microsoft documentation notes that you may need multiple profiles if you want to cover both device-targeted and user-targeted scenarios[3]. However, for simplicity, many organizations assign Edge policies to devices (since browsers are generally used on company devices). Choose the approach that fits your management model.
  • Monitoring deployment: After a broad deployment, use Intune’s reports to ensure all devices have received the policies. Under Reports > Endpoint security or under the baseline profile’s per-setting status, you can identify if any device is in error or conflict. Ideally, all managed devices should show the Edge profile status as “Succeeded”. Any failures should be investigated (e.g., perhaps a PC is offline, or a setting is not applicable to Windows Home edition, etc.).
  • Policy refresh: Intune-managed devices typically check in and refresh policies periodically (every ~8 hours by default, with some variance). If a device is powered off or offline, it will get the Edge policy next time it comes online and syncs. You can expedite testing on a specific device by using “Sync” from the Intune portal (or Company Portal app) for that device.

By thoughtfully targeting groups and monitoring, you can achieve near 100% coverage of your fleet with these Edge security settings. This ensures every user’s browser adheres to your security standards, whether they are in the office or remote.


Managing User Access and Identities in Edge

Securing the browser also involves managing how users access corporate resources through Edge and what they can do with their accounts:

  • Require Azure AD Sign-In for Edge (Work Profile): Encourage or enforce that users sign into Edge with their work (Entra ID/Azure AD) account. This turns on “Edge for Business” mode automatically, separating work browsing from any personal profiles[6]. When signed-in, enterprise policies (like the ones deployed via Intune) are enforced on that profile. You can use Azure AD Conditional Access policies to ensure that only compliant, domain-joined, or Intune-managed devices can access certain resources – indirectly this means they must use the managed Edge (or other compliant apps) to log in. For example, a Conditional Access policy could block access to Office 365 from unmanaged browsers, guiding users to use their Intune-managed device with Edge.
  • Multiple Profile Control: Edge allows multiple browser profiles (e.g., personal and work). Admins can set policies to limit the mixing of profiles, such as disabling the ability to add additional profiles or at least controlling sign-in modes. One policy of interest is ”BrowserSignin” which can force users to sign into Edge with a work account or block personal sign-in. Coupled with “Enterprise Profile Separation”, this ensures work content stays in the work profile. While not always enforced in Business Premium environments, these settings can be considered if data separation is a concern.
  • Permissions and Capabilities: Through Intune’s Edge settings, you can also manage specific browser capabilities for users:
    • For instance, you might disable the Edge Password Manager or Form Autofill for highly sensitive environments, or require a primary password. The security baseline doesn’t outright disable password saving, but it’s something to review based on your org’s password management strategy.
    • You can restrict printing or saving of work data via Edge if needed (e.g., disable printing from Edge to avoid physical data leakage, or restrict downloads to only certain locations).
    • Manage Favorites and data sync: Corporate Entra ID accounts can sync Edge favorites, history, etc. to Microsoft cloud. This is generally useful and encrypted, but some orgs might disable cloud sync for confidentiality. Intune can control that (“Allow syncing of browsing data” policy).
  • Conditional Access App Control: For web apps, Azure AD Conditional Access can integrate with Defender for Cloud Apps to apply session controls in Edge (e.g., preventing downloads of sensitive files via the browser for unmanaged sessions). This is more of an Azure AD/M365 E5 feature, but mentionable as an additional layer if Business Premium customers opt for add-ons: effectively, even if a user is in Edge, the access can be limited by cloud policy if certain risk conditions are met.

In summary, leverage Intune and Azure AD to ensure that Edge is used in a managed, authenticated context. By tying Edge usage to the user’s corporate identity, you gain better control (policies follow the user) and visibility (logs of sign-ins, conditional access reports). Edge for Business will keep personal and work browsing separate[6], reducing the chance of corporate data mixing with personal accounts.


Monitoring and Compliance

After deploying security policies, ongoing monitoring is crucial to maintain Edge’s secure state across all devices.

  • Intune Policy Compliance: Intune provides compliance and configuration reports. Regularly review the Device compliance dashboard in Intune. While Edge settings themselves are configuration profiles (not “compliance policies” in Intune’s terminology), a device’s overall compliance can be tied to whether required settings are in place. For example, you might create a Custom Compliance Policy that checks if a particular registry key (set by the Edge policy) exists, though this is advanced. More straightforward: check each managed device in Intune – under Device Configuration > Setting status, verify that no Edge setting is in error or conflict. Any misapplied setting should be fixed promptly.
  • Security Baseline Compliance: If you used the Edge baseline, Intune has a dedicated report for baseline compliance. It will show each setting and how many devices deviated or had issues. Pay attention to any settings showing non-compliance. Perhaps a user changed something or a machine is missing the policy. Intune can’t usually be “undone” by the user (since these are enforced), but a user might install an unsupported extension if they found a workaround, etc. If an Edge policy was misapplied (e.g., due to concurrent GPO in Hybrid AD scenarios), Intune will flag a conflict.
  • Defender for Endpoint Signals: M365 Business Premium includes Defender for Endpoint (Plan 1). If onboarded, Defender for Endpoint will monitor browser threats. Edge is tightly integrated with Defender – SmartScreen blocks, for instance, are reported. Check the Microsoft 365 Security Center for any alerts related to Edge, such as attempts to visit malicious sites that were blocked. While Plan 1 might not have full Threat & Vulnerability Management, it will still log detected threats. If you see repeated SmartScreen blocks for certain users, that might prompt further training or investigation.
  • Browser Update Compliance: Ensure all devices are running a recent version of Edge. Because Edge auto-updates, this is generally the case if internet access is available. For compliance, you can use Intune Proactive Remediations (a scripting feature) or a reports to see Edge versions installed. If some devices fell behind (perhaps auto-update was disabled or failed), Intune can push an update. One method is to deploy the latest Edge installer as a Win32 app to those devices, but normally enabling auto-update is simpler. Consider implementing the Edge Update policy via Intune that sets Auto-update check period override to a reasonable interval (e.g., every 4 hours)[5], to ensure frequent update checks. Intune doesn’t have a native “Edge version compliance” policy, but you could use Azure AD or Endpoint analytics to query versions.
  • Logging and Auditing: Edge itself produces logs/events for policy enforcement. For example, if an extension is blocked by policy, that event can be found in the Event Viewer under Applications and Services Logs -> Microsoft -> Edge. In a security audit, you might review such logs or use a log aggregator. However, this is typically only done if investigating an incident. Day-to-day, rely on Intune and Defender dashboards for a high-level view.
  • User Feedback Loops: Sometimes users will report an issue (e.g., “I can’t install an extension” or “Edge won’t let me bypass a certificate warning”). These reports are actually signs that your security policies are working! Nonetheless, monitor helpdesk tickets or user feedback to identify if a policy is too restrictive or causing workflow issues. For instance, if a developer legitimately needs a certain extension, you might adjust the allowed list. Monitoring isn’t just technical – it’s also listening to user impact and balancing security with usability.

By actively monitoring these areas, you can verify that your Edge security measures remain effective and that all devices stay in line with the policy. It’s far easier to address compliance drift or new threats early than to remediate after a breach.


Keeping Edge Up-to-Date and Patched

Maintaining the latest browser version is a non-negotiable aspect of browser security. New Edge releases often patch security vulnerabilities and introduce improved defenses. Here’s how to manage updates:

  • Built-in Auto-Update: Microsoft Edge’s built-in updater is the primary mechanism to get updates. By design, Edge will automatically download and install updates in the background for users, without needing full admin rights. This should be kept enabled in all environments. The good news is that, on a standard Windows install, users typically cannot easily disable Edge updates (especially if governed by Intune policies). Verify that no Intune policy or GPO is inadvertently turning off updates. The default (no special policy) is that Edge checks for updates approximately every 12 hours[5]. You can shorten this interval via policy if needed[5].
  • Intune Management of Updates: While there isn’t a dedicated “Edge update” slider in Intune like there is for Windows Update, you can deploy Edge update configurations via Administrative Templates. For instance, using Intune’s administrative template for Edge, set “Update policy override default” or “Target Channel override” if you want to lock Edge to a particular channel (Stable vs. Extended Stable). Small businesses usually stay on the Stable channel. You might also configure “Allow Edge browser to automatically update” (should be enabled) and “Restore failed updates” (Edge can rollback if an update fails, which is fine). Intune can enforce that Edge continues to update itself normally.
  • Forced Updates: In scenarios where a critical fix is out and you want to ensure users restart Edge to apply it, you can send a notice or use Intune’s endpoint analytics messaging or a toast notification script. There is no native Intune button to “reboot all Edge browsers,” because it’s generally not needed (Edge will eventually enforce a restart after update, and users often restart the browser daily). However, in high-security environments, you might instruct users to restart Edge or even schedule a device reboot after a major security update rollout.
  • Update Compliance Monitoring: As part of monitoring, review the Edge versions in use. Microsoft’s Security Center or Defender for Endpoint Threat & Vulnerability Management (TVM)—if you had it—would list outdated browsers as vulnerabilities. Without TVM, you can still periodically generate a report using a script: for example, an Intune Proactive Remediation script can query the version of msedge.exe on devices and report it. Ensure it’s at the expected version (e.g., if the current version is 114.x, no one should be on 112.x). If some devices are lagging significantly, investigate if their update service is broken or if they are rarely online.
  • Edge on Mac and Mobile: Don’t forget non-Windows platforms. Edge on Mac updates via Microsoft AutoUpdate (MAU). Intune on macOS can enforce MAU settings. Edge on iOS/Android updates via the respective app stores – ensure your mobile application management doesn’t block app updates. Generally, encourage users to keep apps updated, possibly using Apple’s managed App Store updates or the Google Play Enterprise management for controlled devices.

In summary, let Edge do its job with automatic updates, and use Intune policies only to monitor or fine-tune if necessary. Keeping browsers patched closes the door on many vulnerabilities attackers might exploit.


Integration with the Microsoft 365 Security Ecosystem

One advantage of standardizing on Edge and Intune is tight integration with other M365 security features. Here are ways the Edge security initiative ties into your broader security landscape:

  • Microsoft Defender for Endpoint (MDE): As mentioned, Edge shares threat intelligence with Defender. For example, SmartScreen phishing blocks in Edge provide signals to your Security Operations Center via Defender[2]. If a user encounters a malicious site, it’s logged and can be correlated with other alerts. MDE can also do web content filtering for any browser, but it has enhanced controls with Edge (e.g., it can block access to certain categories on Edge specifically if configured). With Business Premium’s MDE P1, you at least get basic web threat monitoring. If upgraded to P2, you get vulnerability management that covers Edge settings and version as part of the endpoint’s security score.
  • Microsoft Purview (Data Loss Prevention): Edge has native hooks for Microsoft Purview DLP on endpoints[2]. If your subscription includes Purview DLP (E5 Compliance or an add-on – note: Business Premium might not include full DLP, except possibly for Office apps), Edge can enforce DLP policies such as blocking copy-paste of sensitive info into web forms or preventing uploads of classified files to unsanctioned websites. This is an area to explore if data exfiltration via web is a concern. Even without full DLP, Edge allows basic controls like printing or download restrictions for trusted vs. untrusted sites if you configure it.
  • Azure AD Conditional Access: We touched on this under user access, but to reiterate, CA policies can ensure that only devices with Intune policies (compliant devices) access corporate cloud resources. This means even if a user tries a different browser or an unmanaged machine, they’d be blocked. You can specifically target “Browser” as a client app in Conditional Access rules. If you want to enforce Edge usage, one indirect method is to only allow browsers that support integrated Windows authentication or conditional access authentication contexts – in practice, Edge (and Chrome with a plugin) are the primary ones that do. Many orgs simply require “Require device to be marked as compliant” for web app access, which covers Edge since on an Intune-managed device Edge will be compliant.
  • Global Secure Access / Secure Web Gateway: Microsoft has introduced Microsoft Defender for Cloud Apps and Azure AD Application Proxy, etc., for securing access. While beyond the scope of this report, note that Edge for Business can work with Microsoft’s SSE (Security Service Edge) offerings (such as Global Secure Access) to route traffic through cloud security gateways. In a Business Premium context, you might not have these advanced features, but the ecosystem is ready to integrate if you do invest in them.
  • Logging and Analytics: By using Edge enterprise policies, you gain visibility. For example, signs of abnormal browser usage (mass downloads, visiting risky sites) may surface in logs that feed into Microsoft Sentinel or other SIEM solutions. If you have Sentinel, there are data connectors for Office 365 and Azure AD that, together with Defender logs, can be used to analyze browser usage patterns for anomalies.

In short, securing Edge is not an isolated task – it reinforces and benefits from all other security layers in Microsoft 365. The identity protection, endpoint protection, and information protection features all intersect at the browser. Taking advantage of these integrations can elevate your security posture beyond just configuring Edge settings.


User Education and Awareness

No security configuration is complete without addressing the human factor. While Intune and Edge can enforce many protections, users should be educated on safe browsing practices to complement these technical measures:

  • Train employees to recognize browser warnings: Ensure users understand that Edge’s warnings (Smartscreen blocks, certificate errors) are serious. They should not try to circumvent them. In fact, you have disabled bypass for most warnings in policy[1], but explain why. For example, if Edge shows a red phishing warning, the user should know not to proceed (and in our setup, they can’t). Teaching them the importance of those warnings will reduce any temptation to find workarounds.
  • Phishing awareness: Regular security awareness training should include spotting phishing attempts, not just in email but on the web. Users should be cautious when entering credentials into web pages. Edge will help by identifying known phish sites and showing the domain clearly, but user vigilance is still key. Encourage them to report suspicious web pages to IT.
  • Extensions caution: Since you blocked extensions by default, users might ask “Why can’t I install this add-on?” Educate them that unapproved extensions can pose risks, and there’s a process to request an extension to be allowed if it’s business-critical. This manages expectations and prevents users from attempting to use unmanaged browsers to get an extension (a risk in itself).
  • Personal vs Work browsing: Remind users to separate their work and personal web activities. With Edge’s profile separation, it’s easier – work stuff in the work profile (with your policies active) and personal stuff in a personal profile/browser. Users should avoid logging into work sites on personal browsers or devices, as those wouldn’t have Intune protections. Similarly, discourage them from doing personal sensitive transactions on their work browser session.
  • Policy transparency: Let users know what protections are in place. For instance, inform them that certain file downloads might be blocked if deemed dangerous, certain websites are off-limits, etc. This can prevent frustration and foster a security culture. Many users feel better knowing the organization is actively protecting them with modern tools, as long as they’re aware of the “rules of the road.”
  • Reporting issues: Encourage users to promptly report if they encounter a website needed for work that is being blocked or not functioning due to the browser settings. There may be cases where a line-of-business web app uses an outdated control that got blocked. Rather than the user trying unsafe tweaks, they should alert IT. You can then assess and possibly adjust policy for that site (e.g., allow an exception for an internal site in IE mode if absolutely required, or add a certain URL to Trusted Sites via policy, etc.). A feedback loop helps maintain security without hampering productivity.

Security awareness training should be an ongoing effort – it reinforces that technology alone isn’t a silver bullet. By combining a locked-down Edge configuration with educated, security-conscious users, your defense-in-depth is much stronger.


Ongoing Maintenance and Policy Review

Finally, securing Edge is not a one-time set-and-forget task. Regular maintenance and review will ensure your policies remain effective and up-to-date:

  • Stay updated on Edge baseline changes: Microsoft periodically updates the security baseline for Edge (e.g., with each major release or annually). New settings might be added as security features evolve. For example, in version 128 of Edge’s baseline Microsoft added and removed some settings to keep the recommendations current[4]. When Intune offers a new baseline version, review the change log. Plan to update your baseline profiles to the latest version after testing[3]. New settings could include additional protections you want, and outdated ones might be deprecated.
  • Evaluate new Edge features: Microsoft Edge is continuously improving, including security features (like Enhanced Security Mode, which was introduced to mitigate memory vulnerabilities by disabling JIT for untrusted sites[2]). Keep an eye on Edge release notes. If a new feature could benefit security, consider enabling it via Intune policy. For instance, Enhanced Security Mode can be enforced (it’s the feature that provides extra protection on unfamiliar sites by using hardware-enforced security). The same goes for upcoming features like Edge network isolation improvements, or integration with Windows Defender Smart App Control – as these come, adjust your policies.
  • Revisit exceptions and allowances: Over time, you might grant some exceptions (e.g., allow a specific extension or enable an old protocol for a specific system). Maintain a documented list of these and revisit them periodically. Aim to tighten exceptions if possible (maybe that legacy system got updated and you can remove the exception now). The goal should be to converge back to baseline standards after temporary needs pass.
  • Audit configurations: Perform an audit at least annually (if not quarterly) of your Edge Intune configuration. This means reviewing Intune profiles to ensure they align with current best practices, verifying all device groups are covered, and cleaning up any unused profiles. Microsoft’s documentation and compliance toolkit can help compare your settings with the recommended baseline.
  • Security incidents review: If there were any security incidents or near-misses involving browsers (e.g., a malware download was caught, or a user fell for a phishing page), analyze if additional Edge controls could prevent those in the future. Maybe enabling a stricter download policy, or integrating a threat feed. Use incidents as learning opportunities to refine policy.
  • User feedback and usability: Check in with user representatives or run surveys to gauge if the Edge policies impede work in any way and if so, is there a justified trade-off or a safe adjustment. Browser security is critical, but sometimes overly harsh measures (like completely blocking all downloads) might not be suitable for all roles. Adjust with caution, always weighing risk vs reward.
  • Documentation: Keep your own documentation of what settings are deployed and why. This helps for continuity (e.g., if another admin takes over, or if you liaise with compliance officers). Document any rationale for non-standard configurations.

By maintaining vigilance and adapting to new developments, you’ll ensure that your Edge browsers remain a strong link in your security chain rather than a weak point.


Conclusion

Microsoft Edge is a key application through which users interact with the internet and corporate resources, making it a critical component to secure. By leveraging Microsoft 365 Business Premium’s capabilities – especially Intune – you can transform Edge into a highly secure enterprise browser with minimal impact on user productivity. We covered how to apply best practice settings (like SmartScreen, site isolation, extension control, and more) uniformly via Intune, using the built-in Edge security baseline as a foundation[1]. We walked through deploying these configurations to all devices and highlighted the importance of keeping the browser updated and integrated with other security measures like Defender for Endpoint and Conditional Access.

In addition to technical enforcement, we emphasized user education and ongoing management: a secure configuration today must be maintained tomorrow through updates, policy reviews, and training. Security is an ongoing process, and using the rich toolset in M365 Business Premium, administrators can continuously monitor compliance and address new threats as they arise.

By following the guidance in this report, your organization can confidently provide users with a safe, protected browsing experience in Microsoft Edge – one that shields them from threats, protects sensitive data, and meets the highest security standards in day-to-day work. With Intune and M365 Business Premium, enterprise-grade Edge security is within reach for organizations of all sizes, delivered in a cloud-manageable and scalable way.

References

[1] List of settings for the Microsoft Edge security baseline in Intune …

[2] Microsoft Edge for Business Recommended Configuration Settings

[3] Configure security baseline policies in Microsoft Intune

[4] Edge Browser Security Latest Best Practices Released by Microsoft

[5] Best practice to enforce updates on Microsoft Edge to have the latest …

[6] Secure your corporate data using Microsoft Edge for Business

[7] Deploying a Microsoft Edge security Baseline with Intune

Enforce device compliance and app protection policies on BYOD with M365 Business premium

image

M365 Business Premium is well-suited for this because it includes key components like:

  • Microsoft Intune (Part of Microsoft Endpoint Manager): For Mobile Device Management (MDM) and Mobile Application Management (MAM).

  • Azure Active Directory (Azure AD) Premium P1: Provides Conditional Access policies, which are crucial for enforcement.

  • Information Protection Features: For data security.

Here’s a step-by-step approach, focusing on the least intrusive but effective methods for BYOD:

Core Strategy: Prioritize App Protection Policies (MAM) without Full Device Enrollment (MDM)

This is often the preferred approach for BYOD because it protects corporate data within specific apps without taking full control over the user’s personal device. It respects user privacy while securing business information.

Steps:

  1. Configure App Protection Policies (APP / MAM Policies):

    • Go to the Microsoft Endpoint Manager admin center: (endpoint.microsoft.com)

    • Navigate: Apps > App protection policies.

    • Create Policy: Click “+ Create policy” and select the platform (iOS/iPadOS or Android).

    • Basics: Give the policy a descriptive name (e.g., “BYOD App Protection – Android”).

    • Apps:
      • Target policy to: Select “All Public Apps” or “Selected Apps”. For BYOD, often start with core Microsoft apps (Outlook, Teams, OneDrive, Edge, Office apps). You can add other MAM-enabled apps later.

      • Important: This policy only applies to apps that support Intune App Protection.
    • Data Protection: This is the core. Configure settings like:

      • Prevent backup: Block backing up work data to personal cloud storage (iCloud/Google Cloud).

      • Restrict cut, copy, paste: Control data movement between managed (work) apps and unmanaged (personal) apps. Often set to “Policy managed apps”.

      • Encryption: Ensure app data is encrypted. (Usually enabled by default).

      • Screen capture: Block screen capture for Android (iOS requires device management).

      • Save copies of org data: Prevent saving work files to local/personal storage. Allow saving only to managed locations like OneDrive for Business or SharePoint.

      • Receive data from other apps: Control if managed apps can receive data from unmanaged apps.

      • Open data in Org documents: Control which apps can open work documents.
    • Access Requirements: Define how users access the protected apps:

      • PIN for access: Require a separate PIN (or biometrics) to open the work apps. Configure PIN complexity and timeout.

      • Work or school account credentials for access: Force re-authentication after a period of inactivity.
    • Conditional Launch: Set conditions that must be met for the app to launch (e.g., block rooted/jailbroken devices, minimum OS version, app version).

    • Assignments:
      • Target: Assign the policy to specific Azure AD user groups containing your BYOD users. Do not assign to device groups for MAM-without-enrollment.
    • Review + Create: Finalize and create the policy.
  2. Configure Conditional Access Policies in Azure AD:

    • This is how you enforce the use of protected apps and check device state (even without full enrollment).

    • Go to the Microsoft Endpoint Manager admin center or Azure AD portal: (portal.azure.com)

    • Navigate: Endpoint Security > Conditional Access (in MEM) or Azure Active Directory > Security > Conditional Access (in Azure Portal).

    • Create New Policy:
      • Name: Give it a clear name (e.g., “CA – Require App Protection for Mobile Access”).

      • Assignments > Users and groups: Target the same user groups as your App Protection Policy.

      • Assignments > Cloud apps or actions: Select the specific M365 services you want to protect (e.g., Exchange Online, SharePoint Online, Teams). Start with “Office 365” (which covers multiple services).

      • Assignments > Conditions > Device platforms: Configure this policy to apply only to iOS and Android.

      • Assignments > Conditions > Client apps: Configure this to apply to “Mobile apps and desktop clients” > “Modern authentication clients” > Select “Mobile apps”.

      • Access Controls > Grant:
        • Select “Grant access”.

        • Choose “Require app protection policy”.

        • Optional but Recommended: Also choose “Require approved client app”. This ensures users are using MAM-capable apps (like Outlook Mobile instead of native mail clients).

        • For “Multiple controls”: Select “Require all the selected controls”.
      • Enable policy: Set to “On”.

      • Create: Save the policy.

User Experience with this Approach:

  1. The user installs a managed app (e.g., Outlook) from the public app store.

  2. They sign in with their work (Azure AD) account.

  3. Conditional Access checks if access is allowed. The policy requires an app protection policy.

  4. The user is prompted that their organization protects data in the app. They may be prompted to install the Microsoft Authenticator (on Android) or the Company Portal app (on iOS/Android). Crucially, they do NOT need to fully enroll their device via the Company Portal. The Company Portal app simply needs to be present to receive and report the APP status.

  5. The App Protection Policy settings are applied to the app (e.g., PIN required, copy/paste restrictions).

  6. The user can now securely access work data within that managed app. Their personal apps and data remain untouched and unmanaged.


Alternative/Additional Strategy: Device Compliance (Requires Enrollment – MDM)

If you need stronger device-level controls (e.g., enforcing screen lock complexity on the device itself, checking for device encryption, ensuring minimum OS), you need users to enroll their devices into Intune (MDM). This is more intrusive for BYOD and users might resist.

Steps (If Choosing Enrollment):

  1. Configure Enrollment Restrictions: (MEM Admin Center > Devices > Enroll devices > Enrollment device platform restrictions) Ensure personal iOS/Android devices are allowed to enroll if you intend to support this.

  2. Create Device Compliance Policies: (MEM Admin Center > Devices > Compliance policies)

    • Create separate policies for iOS and Android.

    • Configure settings like: Minimum/Maximum OS Version, Require PIN/Password, Require Encryption, Device Threat Level (if using Defender for Endpoint), Block rooted/jailbroken devices.

    • Assign these policies to user groups.
  3. Modify/Create Conditional Access Policies:
    • Instead of (or in addition to) “Require app protection policy,” add the grant control “Require device to be marked as compliant”.

    • You can combine these: Require a compliant device AND require app protection policy for maximum security on enrolled BYOD devices.

User Experience with Enrollment:

  1. User installs the Company Portal app.

  2. User signs in and follows the prompts to enroll their device. This grants Intune management capabilities over the device.

  3. Intune checks the device against the assigned Compliance Policy.

  4. If compliant, the device is marked as such in Azure AD.

  5. Conditional Access policies check for this compliance status before granting access to corporate resources.

  6. App Protection Policies can still be applied for layered data security within apps, even on enrolled devices.

Summary & Recommendation:

  • For BYOD, start with App Protection Policies (MAM) without enrollment, enforced by Conditional Access requiring App Protection and Approved Client Apps. This provides strong data security within work apps with minimal impact on the user’s personal device.

  • Use Device Compliance Policies (MDM) requiring enrollment only if you have specific, strong requirements for device-level settings and your users consent to this level of management on their personal devices.

  • Always communicate clearly with users about what is being managed and why, especially with BYOD.

  • Test thoroughly with pilot groups before rolling out broadly.

By leveraging App Protection Policies and Conditional Access, Microsoft 365 Business Premium offers a powerful and flexible way to secure corporate data on BYOD smartphones while respecting user privacy.