DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Setting Up a Data Catalog With Azure Purview and Collibra: What Three Attempts Taught Me
  • We Went Multi-Cloud and Almost Drowned: Lessons From Running Across AWS, GCP, and Azure
  • 5 Ways Azure AI Search Enhances Enterprise RAG Architectures
  • Hands-On with Azure Local via the Azure Portal

Trending

  • The Agentic Agile Office: Streamlining Enterprise Agile With Autonomous AI Agents
  • Offline-First Patch Management for 10,000 Edge Nodes: A Practical Architecture That Scales
  • A Scalable Framework for Enterprise Salesforce Optimization: Turning Outcomes Into an Operating System
  • How to Parse Large XML Files in PHP Without Running Out of Memory
  1. DZone
  2. Software Design and Architecture
  3. Cloud Architecture
  4. Azure PowerTip: Fixing ''IP Address Is Not Allowed to Access Server''

Azure PowerTip: Fixing ''IP Address Is Not Allowed to Access Server''

Don't you love it when Azure blocks your IP address' access? No? Oh. Well, let's fix it so that your firewall lets you through to your SQL database.

By 
Manuel Meyer user avatar
Manuel Meyer
·
Apr. 13, 17 · Tutorial
Likes (0)
Comment
Save
Tweet
Share
17.6K Views

Join the DZone community and get the full member experience.

Join For Free

When using SQL databases on Azure, the firewall on the DB server blocks requests from unknown IPs. This means that when you try to connect from a client such as SQL Server Management Studio (SSMS) or Visual Studio, your request to connect to the DB is rejected with the following message:

Cannot connect to mmedb.database.windows.net.

Cannot open server ‘mmedb’ requested by the login. Client with IP address ‘178.197.226.xxx’ is not allowed to access the server.  To enable access, use the Windows Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect. (Microsoft SQL Server, Error: 40615)

image

What you need to do is configure the firewall on the Azure Database Server to allow a connection from your local IP address. Follow these steps:

1. Go to the Azure Portal and navigate to your database.

2. On the blade for your database, click the link to the DB server on the upper right corner.

image

3. Once you are on your DB server's blade, click “Firewall” from the options on the left-hand side.

image

4. On the firewall blade, click the “Add client IP” button on the top. This adds your current IP address to the rule list. Don’t forget to give it a meaningful name in order to be able to remove it later. (If you don’t need it anymore).

image

5. Click “Save”

Note that it can take several minutes even AFTER the setting changes are confirmed in the portal for you to be able to log into your database.

azure

Published at DZone with permission of Manuel Meyer. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Setting Up a Data Catalog With Azure Purview and Collibra: What Three Attempts Taught Me
  • We Went Multi-Cloud and Almost Drowned: Lessons From Running Across AWS, GCP, and Azure
  • 5 Ways Azure AI Search Enhances Enterprise RAG Architectures
  • Hands-On with Azure Local via the Azure Portal

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook