Management Portal |
? |
HTTP/S (?) |
? |
Using the Silverlight Management App |
RDP |
*.cloudapp.net Custom domain This is the default for most RDP listeners. |
RDP |
3389 |
Remote Desktop connection to VMs |
Publish from VS |
*.blob.core.windows.net |
Http/s + ? |
? |
Blob domain for package upload for access of management api |
Webdeploy |
*.cloudapp.net
|
Http/s |
8172 |
Webdeploy from within Studio |
SQL Management |
*.database.windows.net
Port 8443 |
The Database Management API is a REST API. All operation requests are sent encrypted over the Secure Sockets Layer (SSL) and authenticated using X.509 v3 certificates. Database Management API requests can be initiated from within Windows Azure, or directly over the internet from any application that can send HTTPS requests and receive HTTPS responses. All requests are sent to the SQL Azure Database Management Service on port 8443 using the following base URL: https://management.database.windows.net:8443 |
|
TDS |
1433 |
Manage SQL from Management Studio |
Upload into Storage |
*.blob.core.windows.net |
Http/S |
80/443 |
Push data into Azure Storage |
Service Bus Relay TCP Mode |
*.servicebus.windows.net
**EXCERPT** from the developers guide below |
“The relay service only requires a few outbound ports to be open, specifically ports 9350, 9351, 9352, 9353, depending on the features you choose to use, and the standard HTTP ports 80/443. It uses ports 9350 for one-way TCP connections and port 9351 for one-way TCP/SSL connections. They use ports 9352 and 9353 for bidirectional TCP connections and a more advanced connectivity mode we’ll discuss later. It’s important to note that you don’t have to open any inbound ports on your firewall or perform any kind of port mapping on your NAT/router device in order to use the relay service.” |
|
SB over TCP |
9350, 9351, 9352, 9353 |
Listeners on Service Bus Relay over TCP (requires 443 for Access Control token acquisition) |
Service Bus Relay HTTP Mode |
*.servicebus.windows.net |
SB over HTTP |
80 |
Listeners on Service Bus Relay over HTTP (requires 443 for Access Control) |
Service Bus Publish Subscribe |
*.servicebus.windows.net |
SBMP over TCP |
9354 |
Service Bus Queue and Topic clients over TCP (in CTP) |
Service Bus Pubsub over REST |
*.servicebus.windows.net |
HTTPS |
443 |
Service Bus Queue/Topic/Message Buffer over REST |
Access Control |
*.accesscontrol.windows.net
What you can do with port 443 |
By using Windows Azure AppFabric Access Control with SharePoint I can allow users to authenticate not only by Windows Live ID and Active Directory but also Google, Yahoo! and Facebook! |
|
HTTPS |
443 |
Token acquisition and management for Access Control |
AppFabric Cache |
*.cache.windows.net
Session State Provider for Windows Azure Caching |
The Windows Azure session state provider is an out-of-process storage mechanism for ASP.NET applications. This provider enables you to store your session state in an Windows Azure cache rather than in-memory or in a SQL Server database.
|
|
NETTCP |
22233 |
Cache access (out-of-DC access makes sense for external replication into cache) |
|
|
|
|
|