Microsoft Copilot Prompts forIT Admins& SysAdmins_
Ready-to-use prompts for Microsoft 365 Copilot, Security Copilot, Copilot in Intune, and Copilot in Azure. Copy any prompt, fill in the highlighted placeholders, and run it instantly. Built for IT professionals — not marketers.
54prompts
7categories
freealways
No prompts match — try a different keyword or .
Guide — from library to a working Copilot answer
Find a prompt, adapt it to your tenant, and check what comes back.
1Filter
Pick a category — Security Copilot, M365 Admin, Intune, Entra ID, Azure, PowerShell or Helpdesk — or search by keyword.
2Copy
Copy the prompt with one click. Each card shows which Copilot it is written for.
3Fill the placeholders
Replace the [brackets] with your user, device, incident or policy names before you run it.
4Run it in the right Copilot
Paste it into the matching experience, such as Security Copilot, Copilot in Intune or Microsoft 365 Copilot.
5Verify, then share
Check scripts and settings in a test environment first. Got a better prompt? Submit it.
Prompting tips for admins
STRUCTUREWhat a good admin prompt contains
goal
What you want: a summary, a script, a policy, a checklist
context
Tenant, device, user, incident ID, time range
constraints
Read-only, PowerShell 7, no third-party modules
format
Table, numbered steps, or a script with comments
SAFETYBefore you act on an answer
scripts
Read them; run with -WhatIf or in a test tenant first
policies
Start in report-only or audit mode
facts
Check cmdlets and settings against Microsoft Learn
data
Copilot only sees what your account can access
WHEREWhich Copilot for which job
Security Copilot
Incidents, scripts, threat intel, KQL
Copilot in Intune
Devices, policies, compliance
Copilot in Entra
Sign-ins, risky users, Conditional Access
Copilot in Azure
Resources, costs, troubleshooting
Microsoft 365 Copilot
Docs, emails, Teams, and general PowerShell help
Microsoft Copilot prompts for IT admins, explained
This is a free library of 54 ready-to-use Copilot prompts for system administrators, security analysts and helpdesk teams, grouped into seven categories: Security Copilot, Microsoft 365 admin, Intune, Entra ID, Azure, PowerShell and helpdesk. Each prompt is written for a specific Copilot experience, so you can copy it, fill in your own details and run it where it works best.
What makes a Copilot prompt useful for IT work?
Copilot answers are only as specific as the question. A useful admin prompt names the goal, gives the context Copilot cannot guess (tenant, device, user, incident, time range), sets constraints (read-only, a PowerShell version, no third-party modules) and asks for a format you can act on, such as a table, numbered steps or a commented script. The prompts here follow that pattern and use [brackets] for the parts you fill in.
Which Copilot does each prompt need?
Every card names its target. Security Copilot prompts cover incident summaries, script analysis and threat hunting. Copilot in Intune and Copilot in Entra work inside those admin centres on devices, policies, sign-ins and identities. Copilot in Azure helps with resources and troubleshooting. The PowerShell and helpdesk prompts work in Microsoft 365 Copilot. Which of these you can use depends on your licences and on how your organisation has set Copilot up; Microsoft changes the packaging regularly, so check the current licensing on Microsoft Learn rather than relying on a fixed list.
Can I trust what Copilot returns?
Treat it as a draft from a fast colleague. Copilot can invent cmdlets, parameters or settings that do not exist, or mix old and new admin-centre paths. Read every script before running it, try it with -WhatIf or in a test tenant, start new Conditional Access and compliance policies in report-only or audit mode, and check names against Microsoft Learn. Copilot works with your permissions: it only sees data your account can already access, and it cannot do more than you could do yourself.
Customising prompts for your organisation
Replace the placeholders, then add what is specific to you: naming conventions, the baselines you follow (for example CIS or your own), the platforms in scope and the output your team expects. Save the versions that work in a shared document so the whole team gets the same quality of answer.
Submitting a prompt
Use + Submit your prompt to send one in. The form opens an email in your own mail app with the title, category and text filled in; nothing is stored on this site. Remove customer names, tenant IDs and other internal details before you send it.
Free and private
The library is free, with no account and no tracking cookies. Copying a prompt happens in your browser.
Your submission will be reviewed and added to the library. By submitting you agree it can be published here. No personal data stored — this opens your email client. Questions? jasperbernaers.com