Azure Storage Endpoints

Damir Dobric Posts

Next talks:

 

    

Follow me on Twitter: #ddobric



 

 

Archives

When you have provisioned a storage account in Microsoft Azure, the cloud platform will activate several endpoints for you.
These endpoints provide access to all offered storage services: Blob, Table, Queue and File.

To get a better feeling of this you could try PING them to be sure that services are provisioned correctly. Assuming that “xfiles” is the storage account name
you could ping services as follows:

Azure Files endpoint:

ping myxfiles.file.core.windows.net

Pinging file.am3prdstr07a.store.core.windows.net [168.61.61.18] with 32 bytes of data:
Request timed out.

Table Storage Endpoint

ping myxfiles.table.core.windows.net

Pinging table.am3prdstr07a.store.core.windows.net [168.61.61.16] with 32 bytes of data:
Request timed out.

Blob Storage Endpoint

ping myxfiles.blob.core.windows.net

Pinging blob.am3prdstr07a.store.core.windows.net [168.61.61.14] with 32 bytes of data:
Request timed out.

Queue Storage Endpoint

ping myxfiles.queue.core.windows.net

Pinging blob.bl3prdstr02a.store.core.windows.net [138.91.96.142] with 32 bytes of data:
Request timed out.

 

Please don’t be confused with time-outs. Pinging is blocked on Azure firewall. It is also interesting to note that queue endpoint is on a bit different IP address than all other endpoints.


Posted Sep 04 2014, 09:12 PM by Damir Dobric
developers.de is a .Net Community Blog powered by daenet GmbH.