Cloud Engineer Lab
Cloud Engineer Lab
Cloud Engineer Lab
Cloud Engineer Lab
© 2026
10 ChatGPT Prompts Every IT Admin Should Bookmark

10 ChatGPT Prompts Every IT Admin Should Bookmark

Stop writing AI prompts from scratch every time. These 10 ready-to-use prompts cover the most common IT admin tasks — from writing PowerShell scripts and troubleshooting Azure errors to drafting incident reports and explaining policies to non-technical stakeholders.

10 min read
Share

One of the biggest mistakes IT admins make with AI tools is starting from a blank prompt every time. You end up writing something vague, getting a generic answer, and walking away thinking "AI is not that useful."

The fix is simple — save good prompts and reuse them.

I have been collecting and refining prompts for the past year. These 10 are the ones I reach for most often. Each one is tested, copy-ready, and works in ChatGPT, Microsoft Copilot, and Gemini.


How to Use This Guide

Each prompt below is formatted to copy and paste directly. The parts in [square brackets] are placeholders — swap them for your specific details before sending.

The prompts are grouped by task type so you can jump straight to what you need.


Scripting and Automation Prompts

Prompt 1 — Write a PowerShell Script

This is my most-used prompt. It gives you a production-quality script instead of a quick prototype.

Act as a senior PowerShell engineer specialising in Microsoft 365 and Intune.

Write a PowerShell script that:
1. [Describe what the script should do — be specific and step by step]
2. Runs unattended with no interactive login
3. Uses the Microsoft.Graph PowerShell module (latest version)
4. Authenticates using an Entra ID App Registration (Client ID, Tenant ID, Client Secret)
5. Includes try/catch error handling on every major operation
6. Adds clear comments explaining each section
7. Uses descriptive variable names throughout

Environment: PowerShell 7.4 on Windows Server 2022. 
The tenant may have up to [number] managed devices.
Output the results to [describe output — CSV file path, console, email, etc.]

When to use it: Any time you need a new PowerShell script for Intune, Graph API, Exchange, or Azure management.


Prompt 2 — Explain an Error Message

Paste any cryptic Azure, Intune, or PowerShell error and get a plain-English explanation with next steps.

I am an IT admin working with Microsoft 365 and Intune.

I am getting this error:
[Paste the full error message here]

Please explain:
1. What this error means in plain English
2. What the most common causes are
3. What steps I should take to diagnose it
4. How to fix the most likely cause

Keep the explanation simple — assume I understand IT concepts but not deep API internals.

When to use it: Every time you hit an error you have not seen before. Takes 10 seconds to paste and gives you a clear starting point.


Prompt 3 — Review My Script for Bugs

Before running any script in production, use this prompt to get a second opinion.

Act as a senior PowerShell and Microsoft Graph security reviewer.

Review this PowerShell script for:
1. Bugs or logic errors that would cause it to fail
2. Security issues — hardcoded credentials, missing input validation, excessive permissions
3. Performance problems — is it handling large datasets efficiently?
4. Missing error handling
5. Anything that could cause data loss or unintended changes in production

Here is the script:
[Paste your full script here]

List each issue found with a severity rating (Critical / Warning / Suggestion) and explain how to fix it.

When to use it: Before running any new script against a production tenant. The "Critical" findings are worth acting on — the Suggestions are optional.


Documentation and Communication Prompts

Prompt 4 — Write an Incident Report

When something goes wrong, you need to document it clearly and quickly. This prompt gives you a structured incident report in under a minute.

Write a professional IT incident report using the following details:

- Incident title: [Brief title]
- Date and time: [When it started and ended]
- Services affected: [List affected systems or users]
- Root cause: [What caused it]
- What was done to fix it: [Steps taken]
- Impact: [How many users were affected and how]
- Prevention: [What will stop this happening again]

Format it as a professional report suitable for sharing with senior management. 
Use clear headings. Keep technical language minimal.

When to use it: After any unplanned outage or service disruption. Fill in the details and you have a report ready to send in minutes.


Prompt 5 — Explain a Technical Topic to Non-Technical Stakeholders

One of the hardest parts of IT is explaining technical concepts to people who do not have a technical background.

Explain [technical topic — e.g. "Microsoft Intune conditional access policies"] to someone who is not technical. 
They are a senior manager who understands business outcomes but not IT systems.

Use:
- Simple, everyday language (no acronyms without explanation)
- A short analogy that relates to everyday life
- A brief explanation of why this matters to the business
- Maximum 150 words

Do not use words like "API", "MDM", "Azure AD", or "endpoint" without explaining them first.

When to use it: Before presenting to the board, writing IT comms to all-staff, or explaining a project to a non-technical project sponsor.


Prompt 6 — Create a Step-by-Step How-To Guide

When you need to document a process for your team or for end users.

Write a clear, step-by-step how-to guide for [describe the task].

The audience is [describe your audience — e.g. "IT helpdesk staff who are familiar with Microsoft 365 but not Intune"].

Format the guide as:
- A brief one-paragraph overview of what this guide covers and why
- Numbered steps, each written in plain English
- A callout for any step where mistakes are commonly made
- A "you know it worked" confirmation step at the end

Include any specific commands, settings, or clicks that are needed.
Do not skip steps — assume the reader is doing this for the first time.

When to use it: Creating runbooks, onboarding guides, IT self-service documentation, or standard operating procedures.


Troubleshooting and Analysis Prompts

Prompt 7 — Diagnose a Compliance Policy Problem

When a device is showing as non-compliant and you cannot figure out why.

Act as a Microsoft Intune specialist.

A device is showing as non-compliant in Intune but I cannot identify which policy is causing it.

Device details:
- OS: [Windows 11 / iOS / Android]
- Intune compliance policies assigned: [List the policy names or describe the settings]
- What the device details page shows: [Paste any relevant status text from Intune]

Walk me through a structured troubleshooting process:
1. What information should I collect first?
2. What are the most likely causes based on the details I provided?
3. What should I check in the Intune admin centre?
4. What PowerShell commands would help me investigate further?

When to use it: Any time a device is stuck as non-compliant and the Intune admin centre is not giving you a clear reason.


Prompt 8 — Compare Two Technical Options

When you need to make a recommendation between two approaches and want a structured comparison.

I need to recommend between two options for [describe the decision]:

Option A: [Describe first option]
Option B: [Describe second option]

Our environment: [Briefly describe your org — size, Microsoft licences, current setup]
Our priorities: [e.g. "lowest cost", "easiest to manage", "best security", "least user disruption"]

Compare the two options across these dimensions:
- Cost
- Complexity to set up and maintain
- Security
- User experience impact
- Microsoft support and roadmap

Give a clear recommendation at the end with your reasoning.

When to use it: Architecture decisions, tool selection, project planning, or responding to management questions about approach.


Prompt Engineering Prompts

Prompt 9 — Improve a Prompt You Already Have

Use AI to make your prompts better.

I use this prompt regularly with ChatGPT, but I do not always get the results I want:

[Paste your existing prompt here]

The problems I have with the current output are:
[Describe what is wrong or missing — e.g. "too vague", "no error handling", "wrong tone"]

Rewrite the prompt to fix these problems. Explain what you changed and why.
Keep the improved prompt under 300 words.

When to use it: When a prompt is giving inconsistent results, when the output quality is not where you need it, or when you want to make a prompt more reusable.


Prompt 10 — Generate a Prompt for a New Task

When you need a good prompt for something you have not done before.

I need a reusable prompt template for the following task:
[Describe what you want to use AI for]

My context:
- I work in IT / cloud engineering
- I use [ChatGPT / Copilot / Gemini]
- The output will be used for [internal use / sharing with team / sending to management / etc.]

Write a prompt template that:
- Produces consistent, high-quality results every time
- Uses the right structure for this type of task
- Includes placeholder fields I can fill in for each use
- Is under 250 words

Also explain what makes this prompt effective.

When to use it: Any time you have a new repetitive task that you want to use AI for consistently.


Quick Reference Table

Here is a summary of all 10 prompts:

#PromptBest For
1Write a PowerShell ScriptNew automation scripts
2Explain an Error MessageTroubleshooting unknown errors
3Review My Script for BugsPre-production script review
4Write an Incident ReportPost-incident documentation
5Explain to Non-Technical StakeholdersManagement comms and presentations
6Create a How-To GuideRunbooks and IT documentation
7Diagnose a Compliance Policy ProblemIntune compliance troubleshooting
8Compare Two Technical OptionsArchitecture decisions and recommendations
9Improve a Prompt You Already HavePrompt refinement
10Generate a Prompt for a New TaskBuilding new AI workflows

Tips for Getting Better Results

Be specific about your environment. "Microsoft 365 E3 tenant with 2,000 Windows 11 devices" gives much better context than "Microsoft environment." The more specific you are, the more relevant the output.

Paste real data when you can. For error messages, policy names, or script sections — paste the actual text. AI performs significantly better with real content than with vague descriptions.

Always verify technical facts before acting on them. ChatGPT and Copilot can produce confident but incorrect answers, especially for specific Microsoft product features or licence requirements. Cross-check anything important against Microsoft's official documentation.


Summary

These 10 prompts will cover the majority of AI tasks you need as an IT admin. Save them somewhere you can access quickly — a Teams channel, a OneNote page, or a pinned note.

The key to getting value from AI tools is not trying harder — it is asking smarter. A well-structured prompt with good context consistently produces results you can actually use.

CChetan Yamger

Written by

Chetan Yamger

Cloud Engineer · AI Automation Architect · Blogger

Cloud Engineer and AI Automation Architect with deep expertise in Azure, Intune, PowerShell, and AI-driven workflows. I use ChatGPT, Gemini, and prompt engineering to build intelligent automation that improves productivity and decision-making in real IT environments.

AI AutomationAzure & IntunePowerShell & PythonNode.js / Next.jsApplication PackagingPower BIGeminiVDI / WVDGitHub ActionsM365Graph APIPrompt Engineering
Newsletter

Stay in the loop.
New articles, straight to you.

Deep-dive technical articles on Intune, PowerShell, and AI — no noise, no spam.

New article notifications
No spam, ever
Free forever

Discussion

Share your thoughts — your email stays private

Leave a comment

0/2000

Your email is used to prevent spam and will never be displayed.