Any ideas please? 

cmdlet Get-AzureEndpoint at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
VM: ssasnodeaz03
Get-AzureEndpoint : Cannot bind parameter 'VM'. Cannot convert the "ssasnodeaz03" value of type "System.String" to
type "Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM".
At line:1 char:1
+ Get-AzureEndpoint
+ ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Get-AzureEndpoint], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.En
   dpoints.GetAzureEndpoint

Hi,

We are having a virtual network with, currently, 3 machines that communicate with each other quite frequently. However we have now discovered an issue with (we guess) the virtual switch that should manage traffic.

I'd like to know if someone knows a solution to somehow resolve this (static registration of the entry fails).

The following arp tables are a result of this mishap (starting with the incorrect one using `arp -a -v`); 

Interface: 10.4.2.6 --- 0x11
  Internet Address      Physical Address      Type
  10.4.2.1              12-34-56-78-9a-bc     dynamic
  10.4.2.4              12-34-56-78-9a-bc     dynamic
  10.4.2.5              00-00-00-00-00-00     invalid
  10.4.2.255            ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-00-00-16     static
  224.0.0.252           01-00-5e-00-00-fc     static
  239.255.255.250       01-00-5e-7f-ff-fa     static


Interface: 10.4.2.5 --- 0x13
  Internet Address      Physical Address      Type
  10.4.2.1              12-34-56-78-9a-bc     dynamic
  10.4.2.4              12-34-56-78-9a-bc     dynamic
  10.4.2.6              12-34-56-78-9a-bc     dynamic
  10.4.2.255            ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-00-00-16     static
  224.0.0.252           01-00-5e-00-00-fc     static
  239.255.255.250       01-00-5e-7f-ff-fa     static


Interface: 10.4.2.4 --- 0xd
  Internet Address      Physical Address      Type
  10.4.2.1              12-34-56-78-9a-bc     dynamic
  10.4.2.5              12-34-56-78-9a-bc     dynamic
  10.4.2.6              12-34-56-78-9a-bc     dynamic
  10.255.255.255        ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-00-00-16     static
  224.0.0.252           01-00-5e-00-00-fc     static
  239.255.255.250       01-00-5e-7f-ff-fa     static

I have set up a site-to-site VPN between our on-premise Cisco ASA 5510 and Azure, we used the Azure generated script for configuration settings.  We have successfully connected and have a green tunnel in the Azure manage portal, both the ASA and the Azure dashboard are recording data out but no data in.

On my Azure tenancy I have one virtual network with 4 subnets (plus a 5^th gateway subnet) the VNET has an address range of 10.1XX.0.0/21, subnet1 is 10.1XX.1.0/24, subnet 4 is 10.1XX.4.0/24.  I have not configured network security groups yet (although I have created them and subsequently deleted them)

I have created two windows VMs VM1 on subnet1 (10.1XX.1.4) and VM2 on subnet 4 (10.144.4.4)

I RDPed onto one of the VM and found that it is not possible to ping from VM2 to VM1 using the 10.1XX.. (result is “Request timed out”).  However, it possible to use PSPING (a TCP ping utility) whilst specifying the RDP port.  So traffic flows between machines on the Azure VNET.

I have then tried to PSPING from a client machine on my local network to VM1 by IP address on port 3389, this does not work and returns the following: “This operation returned because the timeout period expired.”  Ping returns a request timed out from my client machine.

I have used tracert and it shows the first hop to our firewall that is between the Cisco ASA and my computer but no further successful hops.  Our firewall is configured to route traffic to the 10.1XX.0.0/21 address range through the Cisco ASA.

I have runStart-AzureVNetGatewayDiagnostics.I have done this at two separate times, once when not sending requests to the Azure network and I have run the same and run psping and tracert to VM1.  The first shows very little gateway diagnostic log, as expected, because I am not trying to use the VPN tunnel.  The latter generates some gateway logs.  This suggests to me that our network this end is routing traffic to Azure successfully.

I have checked that NAT-T is enabled on the Cisco ASA, taken down the VPN tunnel and recreated it.

Is there any documentation on the right configuration for setting up a VPN that works between a Cisco ASA and Azure?

Greetings,

Let me preface this by saying that I have checked the documentation for the recommended phase1 configuration and I still cannot complete phase1. My device is an ASA 5520 running 8.4,

Upon sending traffic I receive log messages:

2014-06-02T23:45:14.343085-05:00 hostname.redacted : Jun 02 23:45:14 CDT: %ASA-vpn-5-713904: IP = azure_gateway.redacted, Received an un-encrypted NO_PROPOSAL_CHOSEN notify message, dropping
2014-06-02T23:45:14.343085-05:00 hostname.redacted : Jun 02 23:45:14 CDT: %ASA-vpn-4-713903: IP = azure_gateway.redacted, Information Exchange processing failed

Isakmp SA:

 6   IKE Peer: azure_gateway.redacted
    Type    : user            Role    : initiator
    Rekey   : no              State   : MM_WAIT_MSG2

Relevant config:

crypto ipsec ikev1 transform-set L2L_AZURE esp-aes-256 esp-sha-hmac

crypto map OUTSIDE_VPN 80 match address L2L_AZURE
crypto map OUTSIDE_VPN 80 set peer azure_gateway.redacted
crypto map OUTSIDE_VPN 80 set ikev1 transform-set L2L_AZURE
crypto map OUTSIDE_VPN 80 set security-association lifetime seconds 3600
crypto map OUTSIDE_VPN 80 set security-association lifetime kilobytes 102400000

crypto ikev1 policy 20
 authentication pre-share
 encryption aes-256
 hash sha
 group 2
 lifetime 28800

tunnel-group azure_gateway.redacted type ipsec-l2l
tunnel-group azure_gateway.redacted ipsec-attributes
 ikev1 pre-shared-key key.redacted

I have other ikev1 policies but the one listed should meet the requirements listed here.

Is there something I am missing?

Thanks in advance.

We have been running an Azure to on-premise firewall VPN for about 1.5 years without issue, but the last few days our on-premise network and specifically the AD controllers can not talk to our Azure VM which is also an AD controller, and somethings are not working the way back either

I can ping the Azure VM even with a large packet size, but can not RDP, map a drive, or Http/s to the VM.

In the other direction I can ping from the Azure VM to the on premise servers, and I can map a drive and RDP ok.

As some light things like ping and NSlookup connection but not queries work from the on-premise servers to the Azure VM, so I thought it must have been the MTU, I have tried setting the TCP-MSS to 1350 and MTU to 1350 on both the Azure VM and the on-premise server and the firewall, and its still not working

When I have sniffed the VPN traffic leaving our on-premise network it is getting encapsulated and sent but never received by the Azure VM, I suspected something is blocking it but its not out firewall or the Windows firewall.

As we haven't changed anything on our firewall I suspect something in the Azure virtual networking has changed, or is blocking the traffic.

I havn't recreated the Azure virtual network but that maybe my next option, unless anyone can suggest anything else?

Thanks

Hi

I created a previous post on this but can no longer update it

We are experiencing around 25-35% packet loss over our VPN to Azure. The strange thing is the packet loss goes in chunks, so we could have 50 successful packets and then drop the next 20.

During the packet loss the VPN remains up. We suspected it may be down to the SA lifetime expiring however I have checked and this is not the case

Our firewall is a Juniper SRX650 with JUNOS 11.6.6 installed. I have used the VPN script from the Azure site which was for 11.4R4

Has anyone else experienced connectivity problems to Azure over a JUNOS firewall? I have created the VPN multiple times, both policy and route based and get the same issue each time

Cheers

James

1. We are deploying a cloud service with 2 web role instances and 2 worker role instances.
2. The 2 worker role instances are configured with endpoints on an ILB
3. If we deploy our cloud service to an existing VNet, before the Azure rolling updates the last few days, it works fine.
4. If we deploy our cloud service  to a newly created VNet, after the Azure Rolling Updates the last few days, we get the following error:

VERBOSE: 4:32:26 PM - Begin Operation: Get-AzureDeployment

VERBOSE: 4:32:26 PM - Completed Operation: Get-AzureDeployment

VERBOSE: 4:32:29 PM - Begin Operation: New-AzureDeployment

New-AzureDeployment : BadRequest : Internal Load Balancer usage not allowed for this deployment.

At C:\apps\DeploymentScripts\DeployAzureApplication.ps1:297 char:29

+             $DeployResult = New-AzureDeployment -Verbose -ServiceName $ServiceNa ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : CloseError: (:) [New-AzureDeployment], CloudException

    + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.HostedServices.NewAzureDeploymentCommand

1. We have tried VNets created with Affinity and Resource Groups same error

Charlie

We run websites on-premise and want to check the performance and availability from internet. So we use the PRTG monitoring tool with a "remote probe" on an Azure VM. 

However on most HTTPS URLs that are tested we have the following intermittent error (in the PRTG monitoring):

Error establishing secure connection [TLS10-12] Error connecting with SSL. EOF was observed that violates the protocol [TLS10] Error connecting with SSL. EOF was observed that violates the protocol [SSL3] Error connecting with SSL. EOF was observed that violates the protocol [SSL2] Error connecting with SSL. EOF was observed that violates the protocol

This error only occurs once about every 100 connection attempts, so it is nearly impossible to nail down the source. And it does appear only from an Azure VM (Windows 2012-R2, A2 and A3 size, standard or basic makes no difference). If I move the same monitoring to a Amazon AWS VM or a PC on a home internet connection this error does not occur in the monitoring.

The errors seem to indicate that some firewall or IPS device might be dropping the connection, however this only occurs on Azure. I can't imagine anything that could cause this very strange behaviour, yet it is happening. For now the monitoring is happening from a probe on AWS/amazon, but I really do look for an explanation. 

The machine itself was created with the new azure portal, with a fixed/reserved public IP and only RDP traffic on a high port is allowed from 3 public IPs. All other traffic from the machine is outgoing (to the core PRTG for which it is the probe and to the websites to test for availability).

We have an existing Site to Site VPN setup between our Azure environment and Cisco ASA at our HQ (working without issues).  We are looking to add the Point to Site option, but since the ASA requires a Static gateway, that's not possible.

What are the other options to setup P2S VPN with a Static gateway already enabled?

Hi all,

I'm stuck on a problem and I can't really find a good answer on technet or watching simple YouTube videos (if there are any technet instructional videos for my questions I'd appreciate a link... when I can get to a good fast connection with lots of data allowance I'll go there and download)...

I've spun up an Azure VM and selected something reasonable for my purposes, which is Windows Server 2012 R2.

I've promoted it to domain controller and I'm not really sure what I'm doing here. So I'll move on to the DNS for the moment, unless I need AD DS configured properly first. I have only one admin account and not creating any others for the moment, and use RDP to login and muck around.  It doesn't matter that much right now, since this is just a test/learn environment where I can make a few mistakes, but I hope not big ones :)

First with AD DS, I just set the name of the server in the VM to myapp.local, when making it a new domain forest. I had no idea why or whether I should have set up a new forest.

I've read that Azure VMs usually have DNS managed themselves, and have Virtual IP addresses which may change.  It seems like my VM instance VIP has changed.

Now that I want to move on to DNS, this is where it's getting interesting. How can I verify my VIP changes or make sure it sticks?  Or do I need to get a static IP for it?  I think I can use some kind of publish wizard to make the virtual IP stick and stay permanent, like a static IP, but not sure if that's what I want.

I have a domain name I want to use, like myapp.com. And I want to use my domain registrar's control panel to have that resolve to the IP (or redirect silently) to myapp.cloudapp.net.  I'm given a list of nameservers the registrar has, and I'm kind of stuck.  What IPs to put in?  So I'm thinking I'll make a stub zone, which I think makes sure that I'm using nameservers elsewhere, and that stuff gets copied into the stub zone and updates when it needs to.

So far it looks like I'll have just a NS RR, which will be ns1.myregistrar.net, or something like that.

What I'm really having trouble with is:

1. What is the IP of this new DNS server?  Just any local IP from ipconfig, e.g. 10.0.0.1? Or 127.0.0.1?
   
2. After entering the network mask, what should I use for default gateway?  Same or different address?
3. If the virtual IP changes, how to make it stick, or how to make it return the updated/current virtual IP everytime there's a query for the name?
4. With the registrar, would I enter the current virtual IP as the domain's primary and secondary nameserver after configuring DNS on the Azure hosted server? Would I need to find an option that supports dynamic IPs?
5. Or with the registrar, once I get the DNS up on the Azure server, would dns1.whatever and dns2.whatever work, unless it somehow requires IP addresses?

I hope this question makes sense... essentially, is my virtual IP going to stay the same somehow (it seems to change), how to configure the host in AD DS and whether it should be a new forest, how to configure the DNS and what zones should I add and configure, and what should I do at my registrar end to make myapp.cloudapp.net the same thing as myapp.com?

After that I need to configure IIS, but I'll leave that for now until I get my head around ADDS and DNS.

Thanks very much for any pointers/tips or advice.

To configure DKIM domain keys, you have to create TXT records of the name "_domainkey.example.com", for example. However, New-AzureDnsRecordSet -Name "_domainkey" -RecordType TXT... fails with the error "BadRequest: The domain name '_domainkey.example.com' is invalid".

Underscores are not valid for hostnames, but are valid in DNS records. The -RecordType SRV seems to have an exception that allows underscores, but not -RecordType TXT. Please fix this or else we cannot properly configure our DNS.

Thanks.

Ron Peters Red Folder, Inc

So we have a cloud service that connects to an on-premise SQL Server 2014 DB over a point to site VNET. Here's the connection string we are using in the web.config of the web role that we have:-

<add name="DefaultConnection2" connectionString="Data Source=<<VPN IP of DB>>,<<port on which SQL Server is running>>;Initial Catalog=<<DB name>>;Integrated Security=False;User ID=<<user_name>>;Password=<<password>>;Trusted_Connection=False;" providerName="System.Data.SqlClient" />

The aforementioned connection string runs on my localhost completely fine. However, after uploading on the azure cloud service, whenever I try to connect using this connection string, I get an exception.

[SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found....

I am able to:-

1) ping from local machine(on which DB is hosted) to Cloud Service VM

2) ping from Cloud Service VM to local machine

3) access files using local machine's computer name (\\<machine-name>) & IP address and vice-versa.

What am I doing wrong? I have tried to use the host name(or computer name) in the data source(which works completely fine on the localhost) but I get the same exception on the cloud. 

Also, I don't have my own DNS server and am using the azure-provisioned one. Instance name of the DB is the default(MSSQLSERVER). TCP/IP connections is enabled for this instance, but Named Pipes isn't..

I am trying to create Virtual Network with Point-to-Site VPN connection by using API. I've done the Virtual Network creation step but stumble on the setting-up Gateway. I can do it manually but when I call API it's always failing by saying "400 Bad request". 

The x-ms-version I am using is 2012-03-01 

The body of the POST looks like this:

<?xml version=\"1.0\" encoding=\"utf-8\"?>
<CreateGatewayParameters xmlns="http://schemas.microsoft.com/windowsazure">
<GatewayType>DynamicRouting</GatewayType>
</CreateGatewayParameters>

And the URL is:  https://management.core.windows.net/{my_ID}/services/networking/{virtualNetworkName}/gateway

Can somebody see an issue with that?

Thanks,

Alex 

Hello,

I am attempting to use the Set-AzureNetworkSecurityGrouptoSubnet  cmdlet however am receiving the following error:

Set-AzureNetworkSecurityGroupToSubnet : BadRequest: The virtual network name 10.11.x.x is not valid.

I have tried explicitly defining the VNET name and using a $vnetname variable, neither of which have worked. I can however, run Get-AzureVNetSite -VNetName 10.11.x.x and I receive a valid response, so the VNET name appears to be perfectly valid.

From what I've read, the VNET name cannot be modified and it appears to me that the only place in which the virtual network name is not valid is when using this cmdlet.

Can anybody help?

I created a site-to-site vpn connection between local ASA(5512, OS 9.1) and Azure. it seems phase 1 and 2 is up but I can't ping from any side and Azure portal shows 0 for data in and some bytes for data-out.

I checked this article below for the same issue and checked what it suggests but seems find on my end. I can't figure out where is wrong.

http://social.msdn.microsoft.com/Forums/windowsazure/en-US/a17ffd32-b712-46d5-90e5-6c4f470f36f6/virtual-network-no-data-in?forum=WAVirtualMachinesVirtualNetwork

Can anyone help on this?

<<<<related configuration on ASA>>>>>>
object-group network azure-networks
 network-object 10.1.2.0 255.255.255.0
object-group network onprem-networks
 network-object 172.18.100.0 255.255.255.0

access-list azure-vpn-acl extended permit ip object-group onprem-networks object-group azure-networks
nat (INSIDE,OUTSIDE-MAIN) source static onprem-networks onprem-networks destination static azure-networks azure-networks
access-group azure-vpn-acl in interface OUTSIDE-MAIN

crypto ipsec ikev1 transform-set azure-ipsec-proposal-set esp-aes-256 esp-sha-hmac
crypto ipsec security-association lifetime seconds 3600
crypto ipsec security-association lifetime kilobytes 102400000

crypto map azure-crypto-map 10 match address azure-vpn-acl
crypto map azure-crypto-map 10 set peer xxx.xxx.xx.xxx
crypto map azure-crypto-map 10 set ikev1 transform-set azure-ipsec-proposal-set
crypto map azure-crypto-map interface OUTSIDE-MAIN

crypto isakmp identity address
no crypto isakmp nat-traversal    ;tried with crypto isakmp nat-traversal as well but the same result.
crypto ikev1 enable OUTSIDE-MAIN
crypto ikev1 policy 10
 authentication pre-share
 encryption aes-256
 hash sha
 group 2
 lifetime 28800

tunnel-group xxx.xxx.xx.xxx type ipsec-l2l
tunnel-group xxx.xxx.xx.xxx ipsec-attributes
 ikev1 pre-shared-key *****

sysopt connection tcpmss 1350

<<<<<<<Azure network configuration>>>>>>>

<NetworkConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/ServiceHosting/2011/07/NetworkConfiguration">
  <VirtualNetworkConfiguration>
    <Dns>
      <DnsServers>
        <DnsServer name="Azure Local DNs" IPAddress="10.1.2.4" />
      </DnsServers>
    </Dns>
    <LocalNetworkSites>
      <LocalNetworkSite name="Tishman_Local">
        <AddressSpace>
          <AddressPrefix>172.18.100.0/24</AddressPrefix>
        </AddressSpace>
        <VPNGatewayAddress>xx.xxx.xx.xxx</VPNGatewayAddress>
      </LocalNetworkSite>
    </LocalNetworkSites>
    <VirtualNetworkSites>
      <VirtualNetworkSite name="TishmanVN" AffinityGroup="TishmanAG">
        <AddressSpace>
          <AddressPrefix>10.1.2.0/24</AddressPrefix>
        </AddressSpace>
        <Subnets>
          <Subnet name="Subnet-1">
            <AddressPrefix>10.1.2.0/25</AddressPrefix>
          </Subnet>
          <Subnet name="GatewaySubnet">
            <AddressPrefix>10.1.2.128/29</AddressPrefix>
          </Subnet>
        </Subnets>
        <DnsServersRef>
          <DnsServerRef name="Azure Local DNs" />
        </DnsServersRef>
        <Gateway>
          <ConnectionsToLocalNetwork>
            <LocalNetworkSiteRef name="Tishman_Local">
              <Connection type="IPsec" />
            </LocalNetworkSiteRef>
          </ConnectionsToLocalNetwork>
        </Gateway>
      </VirtualNetworkSite>
    </VirtualNetworkSites>
  </VirtualNetworkConfiguration>
</NetworkConfiguration>

Hi there,

i'm in the process to migrate our DNS to Azure DNS. After 10 DNS-Zones i get the following error:
New-AzureDnsZone : Conflict: You have reached or exceeded the maximum number of zones in subscription xxx. You have 10 zones of 10 allowed.

Is this because Azure DNS is in preview? Or how can i raise that limit? We have a MSDN Premium (Ultimate) Abonnement.

Thank you in advance
F.Brem

Hello,

I'm having problems getting NSGs to work on my VMs located in my VNet. I have a VNet that has P2S and S2S connections running. I'd like to implement NSG at the subnet level to deny Internet to the VNet and then use NSGs at the VM level to control fine-grained access for inter-subnet traffic. The subnet-level NSG works fine. However, when I associate a NSG to a VM with one rule - DENY ALL, I am still able to access the VM (ssh, https, etc.) Has anyone else experienced this problem? I'm in US East 2.

Here is my subnet-level NSG

   Type: Inbound

Name                 Priority  Action   Source Address  Source Port   Destination      Destination    Protocol
                                        Prefix          Range         Address Prefix   Port Range
----                 --------  ------   --------------- ------------- ---------------- -------------- --------
P2S VPN              200       Allow    192.168.5.0/24  *             *                *              *
S2S VPN              210       Allow    172.16.0.0/25   *             *                *              *
DENY_INTERNET        3500      Deny     INTERNET        *             *                *              *
DENY ALL             4096      Deny     *               *             *                *              *
ALLOW VNET INBOUND   65000     Allow    VIRTUAL_NETWORK *             VIRTUAL_NETWORK  *              *
ALLOW AZURE LOAD     65001     Allow    AZURE_LOADBALAN *             *                *              *
BALANCER INBOUND                        CER
DENY ALL INBOUND     65500     Deny     *               *             *                *              *

And my VM level NSG

   Type: Inbound

Name                 Priority  Action   Source Address  Source Port   Destination      Destination    Protocol
                                        Prefix          Range         Address Prefix   Port Range
----                 --------  ------   --------------- ------------- ---------------- -------------- --------
DENY ALL             4096      Deny     *               *             *                *              *
ALLOW VNET INBOUND   65000     Allow    VIRTUAL_NETWORK *             VIRTUAL_NETWORK  *              *
ALLOW AZURE LOAD     65001     Allow    AZURE_LOADBALAN *             *                *              *
BALANCER INBOUND                        CER
DENY ALL INBOUND     65500     Deny     *               *             *                *              *

Hi All

I Hace recently set up a point to site VPN connection to my azure hosted servers, made my own certs connects fine uunder Windows 7 Pro, have now installed the vlient under Windows 8.1 Pro and now recive this error whern I try to connect to the VPN connection.

A certificate chain processed but terminated in a root certificate which is not trusted by the trust provider.
 (Error 0x800b0109) For customised troubleshooting information for this connection, click Help.

Like I said the connection runs fine under Windows 7 have deledted and reimported all certs and they rexist in both trusted and personla folders such as it is under Windows 7.

can any body help ?

Hi,

Can we add multiple NIC cards in an Azure VM? If yes, how?

If no:

1. there are a lot of apps even from Microsoft which request multiple nic cards.

2. Why this is not supported? Hyper-V supports multiple NIC cards on a VM!

3. When this functionality can be included with Azure.

It provides a lot of architecture challeges and when compared to other Cloud providers like AWS

Any ideas please? 

cmdlet Get-AzureEndpoint at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
VM: ssasnodeaz03
Get-AzureEndpoint : Cannot bind parameter 'VM'. Cannot convert the "ssasnodeaz03" value of type "System.String" to
type "Microsoft.WindowsAzure.Commands.ServiceManagement.Model.IPersistentVM".
At line:1 char:1
+ Get-AzureEndpoint
+ ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Get-AzureEndpoint], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.En
   dpoints.GetAzureEndpoint