◆ Microsoft Azure

Create a workflow in Teams

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 taskSet up a new channel in Teams for the 'Q3 Sales Review' project. Add Sarah, David, and Emily as…+
Set up a new channel in Teams for the 'Q3 Sales Review' project. Add Sarah, David, and Emily as members, and create a shared folder for the sales reports. Make sure it's ready for our 9 AM meeting on Tuesday.
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 create this new Teams channel for the Q3 Sales Review, think about how to best…+
Before I create this new Teams channel for the Q3 Sales Review, think about how to best organize it for easy information retrieval. We always struggle to find the latest reports. Suggest a channel structure and file naming convention that will make it simple for everyone to find what they need, especially the final presentation.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe project manager just told me that despite setting up the new Teams channel, nobody is…+
The project manager is complaining that nobody is using the new Teams channel.
The project manager just told me that despite setting up the new Teams channel, nobody is actually using it for discussions or file sharing, and they're still relying on email. I'm afraid this project will fall behind schedule if communication doesn't consolidate. What's the most common reason people resist new channels, and what's the best next move to encourage adoption without forcing it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently set up new Teams channels that either go unused or quickly devolve into…+
I often create Teams channels that end up unused or become chaotic.
I frequently set up new Teams channels that either go unused or quickly devolve into disorganized chaos, making it hard to track decisions or find files. This wastes my time and frustrates the team. What habit should I change in how I initiate and structure these channels to ensure they become productive, central hubs for collaboration?
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.