Microsoft 365 and Office | Access | Development
The creation and customization of database applications using Microsoft Access
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 42%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
No， it doesn't support to change the port
Can I change Azure SQL Server port 1433 to a different port (Connecting externally using MS Access ODBC)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 95%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETW%3C/text%3E%3C/svg%3E)
T West
136
Reputation points
Hi,
Our IT has flagged port 1433 as being high risk and has requested that we change the way we connect our Access DB to our Azure SQL server. Currently we are connecting using the standard ODBC connection string. Any ideas or information would be greatly appreciated.
Thanks,
Ant
Microsoft 365 and Office | Access | Development
Microsoft 365 and Office | Access | For business | Windows
Microsoft 365 and Office | Access | For business | Windows
A family of Microsoft relational database management systems designed for ease of use.
{count} votes
-
Gustav 722 Reputation points MVP2025-10-19T07:03:28.5466667+00:00 If still not solved at this date, your IT needs an update. The port 1433 risk was/is related to in-house servers. Azure SQL is a very different animal though it closely acts and behaves like a normal SQL Server. Also, the security of Azure SQL is handled by Microsoft, not your IT, and - be asured - is managed with great care.
If still refusing to serve you, ask your IT for having a VPN connection to the server established. This is easy to set up, only adds additional costs and slightly lower speed.
Sign in to comment
2 answers
Sort by: Most helpful
-
-
George Hepworth 22,130 Reputation points Volunteer Moderator2025-10-15T20:35:28.08+00:00 Unlike other SQL Server instances, apparently Azure SQL only supports 1433.
But, it seems to me that, if your IT department is the instigator of this change, your IT department should also be responsible for it. After all, IT is the department tasked with managed this stuff for the organization, not the developer.
Ask them for their guidance on how to proceed. Maybe you can suggest they read the Azure SQL documentation as a first step.