A Windows Azure application is activated for Windows Azure Connect
A corporate policy blocks Internet traffic for local servers.
You need to recommend the firewall rule that will allow Windows Azure Connect traffic for local servers.
What should you recommend?

A.
Allow TCP port 443 inbound.

B.
Allow TCP port 3389 outbound.

C.
Allow TCP port 3389 inbound.

D.
Allow TCP port 443 outbound.

Explanation:
In Windows Azure Connect, the firewall settings on local endpoints (local computers or VMs) are under your control. Windows Azure Connect uses HTTPS, which uses port 443. Therefore, the port that you must open on local endpoints is TCP 443 outbound. In addition, configure program or port exceptions needed by your applications or tools.

Note then when you install the local endpoint software, a firewall rule is created for Internet Control Message Protocol version 6 (ICMPv6) communication. This rule allows ICMPv6 Router Solicitation and Router Advertisement (Type 133 and Type 134) messages, which are essential to the establishment and maintenance of an IPv6 local link. Do not block this communication.

When you activate a role for Windows Azure Connect, the firewall settings for the role are configured automatically by Windows Azure. In addition to these firewall settings, you might need to configure program or port exceptions needed by your applications or tools. Otherwise, we recommend that you do not change the firewall settings on an activated role.