◆ Microsoft Azure

Create an onboarding checklist for employees

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate an onboarding checklist for the new hire, Alex, covering access to the dev environment,…+
Create an onboarding checklist for the new hire, Alex, covering access to the dev environment, Slack channels, and HR paperwork, due by his start date next Monday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I finalize this onboarding checklist for new engineers, make sure it covers all critical…+
Before I finalize this onboarding checklist for new engineers, make sure it covers all critical security training modules and compliance checks, and flag any steps that commonly cause delays for new hires.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm putting together the onboarding checklist for Sarah, our new Senior Cloud Engineer. I've…+
I'm creating an onboarding checklist, but I'm unsure if I've missed a critical security step for cloud access.
I'm putting together the onboarding checklist for Sarah, our new Senior Cloud Engineer. I've included standard access, but I'm worried I've overlooked a crucial security step for privileged cloud access that could leave us vulnerable. I can't afford a security lapse. What's the most common security oversight in these checklists, and how can I verify I haven't missed it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur onboarding checklists frequently miss critical steps, causing new hires to wait for access…+
New hire onboarding checklists often miss critical steps, leading to delays and security risks.
Our onboarding checklists frequently miss critical steps, causing new hires to wait for access or creating security gaps weeks after they start. It's frustrating for everyone and reflects poorly on our team. What habit should I change in how I create or review these checklists to ensure they are consistently comprehensive and secure from day one?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Microsoft Azure's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.