◆ Microsoft Azure

Allow IP address to access SQL server

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 taskAdd an inbound firewall rule to the 'SalesDatabaseServer' SQL server to allow access from IP…+
Add an inbound firewall rule to the 'SalesDatabaseServer' SQL server to allow access from IP address '203.0.113.45'.
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 add this new IP address '198.51.100.12' to access the 'CustomerData' SQL server, help…+
Before I add this new IP address '198.51.100.12' to access the 'CustomerData' SQL server, help me ensure I'm not creating any security gaps. I need to make sure this access is strictly necessary and properly documented, considering our compliance requirements. What are the key security considerations and best practices when granting new IP access to a production SQL server?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA vendor just reported they can't connect to our 'ReportingDB' SQL server from their new office…+
A vendor just reported they can't connect to our 'ReportingDB' SQL server from their new office IP.
A vendor just reported they can't connect to our 'ReportingDB' SQL server from their new office IP address, which they just gave me as '203.0.113.10'. I added it to the firewall rules, but they still can't connect. Our weekly data sync depends on this, and it needs to run by end of day. I'm not sure if it's a caching issue or something I missed. What's the most likely reason for this persistent connection failure after adding an IP, and how can I quickly verify and fix 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 face issues with external partners and new services unable to connect to our SQL…+
I frequently face issues with external partners unable to connect to our SQL servers due to firewall rules.
I frequently face issues with external partners and new services unable to connect to our SQL servers, usually due to incorrect or missing firewall rules. This leads to urgent, reactive troubleshooting and delays in critical integrations. What habit can I change or what proactive step can I take to ensure a more reliable and efficient process for managing SQL server firewall access, preventing these recurring connectivity problems?
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.