◆ Microsoft Azure

Care for fraud prevention

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
See the prompt↓All Microsoft Azure tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskImplement the new IP reputation list from the threat intelligence feed into the WAF for the…+
Implement the new IP reputation list from the threat intelligence feed into the WAF for the 'eCommerce-prod' application gateway. Configure it to block all traffic from those blacklisted IPs immediately.
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 activating this new fraud prevention rule on the WAF, run a dry-run or simulation…+
Before activating this new fraud prevention rule on the WAF, run a dry-run or simulation against our recent traffic logs. Flag any legitimate customer traffic that would be blocked by this rule, so we can tune it before it goes live and impacts real buyers.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe just enabled the new fraud prevention rule in the WAF, and now customer support is reporting…+
After enabling the new fraud rule, we're seeing an unexpected spike in customer support tickets about failed payments.
We just enabled the new fraud prevention rule in the WAF, and now customer support is reporting a sudden spike in failed payment transactions. The WAF logs show blocks, but I can't immediately tell if it's legitimate fraud or if the new rule is too aggressive and catching real customers. I'm worried about losing sales, but also about letting real fraud through if I disable it. What's the fastest way to diagnose if it's a false positive issue and what's the best immediate action?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time we roll out a new fraud prevention rule, we inevitably block some legitimate users,…+
New fraud rules often cause unintended blocks for legitimate users, leading to customer churn.
Every time we roll out a new fraud prevention rule, we inevitably block some legitimate users, leading to angry customers and lost revenue. This erodes trust and makes security look like a barrier. What habit should I change to better validate and test new fraud rules before deployment, ensuring we catch bad actors without impacting our real buyers?
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.