Fixed end point for Azure Data Lake.


  • Hi, 

    In order to write data to Azure Data Lake(ADL) programmatically, I believe there are three end points being used.

    1. token end point

    2. redirect url

    3. final end point to the ADL

    We have a fire wall in our production and need to whitelist those three end points where "3" can change based on what we get from "2". Is there a way to get fixed end point of "3"?



    Thursday, February 9, 2017 5:47 PM

All replies

  • Isn't 3 the same as <youraccount> ? Do you have an example of 1, 2, 3 in your context?



    Friday, February 10, 2017 5:19 AM
  • Hey Amit,

    When I played with ADL with REST API, I get <storename> on 3.

    However, I am not sure it is a contract that it will be always like this. Judging from REST API doc advises to always get the redirect URL, I would guess 3 can change. Otherwise, why would we need to have step 2?

    Furthermore, I wonder store name is unique. If it's not unique step 3 would provide some unique endpoint, would not?

    (My store name is "mytestdatalakestore" and step 3 provides



    Friday, February 10, 2017 6:26 PM
  • Hi Jin,

    The store name by virtue of it being part of the DNS name, is unique. From firewall purposes, you should be ok to assume that will be returned at step 3.



    Saturday, February 11, 2017 2:58 AM