Looking for clarification about the subnets that Azurestack uses ( , , RRS feed

  • Question

  • Looking to clarify how Azurestakc is ising the , , subnets

    The documentation states :-


    Do not connect the POC machine to the subnets,, or These are reserved for the internal networks within the Microsoft Azure Stack POC environment

    I'm planning to put ws2016 with Azurestack on top on one our vlans. However we already use within our company. If I read this correctly, I can still continue to deploy Azurestack with no effect to our network as its "Internal". So we won't get any conflicts? Have I got that right?

    Wednesday, July 13, 2016 1:55 PM


All replies

  • Hello,

    Connecting to would create conflict as these are reserved for the Azure Stack POC. And as the instructions mention, the POC should NOT be connected to these subnets.


    Thursday, July 14, 2016 9:46 AM
  • Thanks, I may being stupid here but still not quite sure about this.

    So this network is "visible" if thats the right term?

    The notes mention it's used internally, I guess what I'm trying to establish is when it says internal, does it effect out network used elsewhere?

    What does it mean by internal?

    APoligies If I'm asking a daft question, just need to get thsi clear in my head as it basically determines whether we can put this POC on our current network or whether we need to isolate so it doesn't cause issues with our current network.

    Thursday, July 14, 2016 9:55 AM
  • Hi Andrew, series you can hide it from POC network and you can use it also. BUT *** if by any chance the network is exposed your infra will go for a toss.  I have tested in my LAB and I can share this experience with you. You should NOT use it.

    Even if natting the IP's help to hide your private and public network with respective to POC, still would be a wrong decision. Anyways the environment is POC now . You can always have a restricted lab setup. 



    Friday, July 15, 2016 8:11 AM
  • Thanks for the replies guys.

    Friday, July 15, 2016 8:47 AM