◆ Microsoft Azure

Create new user in SQL Azure database

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 taskCreate a new user, 'ReportingServiceUser', in the 'SalesData' SQL database with read-only…+
Create a new user, 'ReportingServiceUser', in the 'SalesData' SQL database with read-only permissions to the 'Customer' and 'Orders' tables. Set a strong password and ensure it expires in 90 days. Send the connection string to David in BI by Friday.
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 user for the SalesData database, help me make sure it won't cause any…+
Before I create this new user for the SalesData database, help me make sure it won't cause any security headaches. Suggest the least permissive roles needed for read-only access to 'Customer' and 'Orders', and flag any potential privilege escalation risks or common misconfigurations I should watch for.
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 trying to create a new user for the 'Analytics' application in our 'ProductionDB' SQL…+
I just tried to create a new user for our new analytics tool, but it keeps failing with a permissions error on the master database.
I'm trying to create a new user for the 'Analytics' application in our 'ProductionDB' SQL database, but it keeps failing, saying I don't have permission on the master database. I'm logged in with my usual admin account, which usually works. The analytics team needs this by end of day, and I'm worried about blocking them. What's the likely diagnosis for this master database permission issue when creating a user, and what's the best next step to get this user created without over-privileging 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 keep losing hours trying to debug permission errors whenever I create new users or assign…+
I keep spending too much time trying to debug permission errors when creating new database users or assigning roles.
I keep losing hours trying to debug permission errors whenever I create new users or assign roles in a SQL database, especially for cross-database access. I often over-provision initially just to get it working, then have to pare it back. What habit should I change to ensure I get the permissions right the first time, or at least diagnose issues faster, without compromising security?
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.