How to get the IP Address for Azure DevOps Hosted Agents to add to the white list
4
Is there a way to the IP address range for the hosted machine running?
This is related to the Release Pipeline -> Hosted agent.
Issue: Getting access denied on connection, as the connection is getting refused via Firewall. Need to whitelist the IP address range for this request coming from release pipeline on DevOps.
azure-devops azure-pipelines edited Nov 22 '18 at 8:58
Armali
7,7881238107
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
add a comment |
4
Is there a way to the IP address range for the hosted machine running?
This is related to the Release Pipeline -> Hosted agent.
Issue: Getting access denied on connection, as the connection is getting refused via Firewall. Need to whitelist the IP address range for this request coming from release pipeline on DevOps.
azure-devops azure-pipelines edited Nov 22 '18 at 8:58
Armali
7,7881238107
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
add a comment |
4
4
4
3
Is there a way to the IP address range for the hosted machine running?
This is related to the Release Pipeline -> Hosted agent.
Issue: Getting access denied on connection, as the connection is getting refused via Firewall. Need to whitelist the IP address range for this request coming from release pipeline on DevOps.
azure-devops azure-pipelines edited Nov 22 '18 at 8:58
Armali
7,7881238107
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
Is there a way to the IP address range for the hosted machine running?
This is related to the Release Pipeline -> Hosted agent.
Issue: Getting access denied on connection, as the connection is getting refused via Firewall. Need to whitelist the IP address range for this request coming from release pipeline on DevOps.
azure-devops azure-pipelines azure-devops azure-pipelines edited Nov 22 '18 at 8:58
Armali
7,7881238107
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
edited Nov 22 '18 at 8:58
Armali
7,7881238107
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
edited Nov 22 '18 at 8:58
Armali
7,7881238107
edited Nov 22 '18 at 8:58
Armali
7,7881238107
edited Nov 22 '18 at 8:58
Armali
7,7881238107
7,7881238107
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
asked Nov 22 '18 at 0:41
Gagan Jeet SinghGagan Jeet Singh
316
316
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
4
I have a step in a release that gets the Hosted Agent IP address in powershell with:
Invoke-RestMethod http://ipinfo.io/json | Select -exp ip
Hope that helps.
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
For an Ubuntu based VM this is the equivalent command for e.g. a step as a bash script:curl -s http://ipinfo.io/json | jq '.ip', then you can compare the IP address with the CIDR ranges in the XML file at microsoft.com/en-nz/download/details.aspx?id=41653 (be aware it changes weekly, as stated in the other answer). Does anyone know if there is a config/setting page on AzureDevops to know this information without running commands?
– TPPZ
Jan 29 at 11:04
@TPPZ You, me and everybody else is suffering from the same problem. There used to be an API-call (beta/labs) to get agent information, but it has been dropped. Eye-balling the API-docs don't reveal anything useful.
– Jari Turkia
Mar 4 at 11:41
@JariTurkia if it can help with this pain: whatever thing is on Azure that needs to be accessed by the hosted VM on AzureDevOps e.g. a database can have a firewall rule that allows0.0.0.0(cf. docs.microsoft.com/en-us/rest/api/sql/firewallrules/…). This is some sort of special wildcard in the Azure land to avoid updating IPs due to that XML list I was mentioning. In my scenario my Azure DevOps pipeline with the hosted VM was supposed to create/access a SQL Server instance on Azure. When adding the firewall rule in the SQL Server definition, then all good
– TPPZ
Mar 4 at 15:21
add a comment |
1
We need to white list the IP address used by the Azure Datacenters in the list mentioned below:
https://www.microsoft.com/en-nz/download/details.aspx?id=41653
Note: This list gets updated every week, so please be mindful of this during the deployment planning
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
If you need to white list these IPs in the firewall rules for other Azure services, then you could just use the work around of start/stop IP range0.0.0.0as explained here: docs.microsoft.com/en-us/rest/api/sql/firewallrules/… this way you don't need to update the IP list according to the XML downloaded weekly from microsoft.com/en-nz/download/details.aspx?id=41653
– TPPZ
Jan 29 at 11:39
add a comment |
0
Use a script step in the pipeline to get the current external ip and whitelist it. after pipeline finishes use another script step to clean up.
Thats the only way (for hosted agent), unfortunately.
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
There is an article article around the IP ranges for VSTS/AzureDevOps used by the Microsoft Azure Datacenters (microsoft.com/en-nz/download/details.aspx?id=41653) which change every week. There is a PublicIP xml file for each region which we need to whitelist during any deployment
– Gagan Jeet Singh
Nov 26 '18 at 22:54
this is a real overkill
– 4c74356b41
Nov 27 '18 at 4:42
Thanks for the update and help. The above answer might not work as the customer has to know the IP address up-front in order to White list this. Getting the IP address from the script and then wait for the customer to add it to the White List will not work. So white listing the IP range worked for us.
– Gagan Jeet Singh
Nov 28 '18 at 21:37
might as well whitelist 0.0.0.0
– 4c74356b41
Nov 29 '18 at 5:36
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422395%2fhow-to-get-the-ip-address-for-azure-devops-hosted-agents-to-add-to-the-white-lis%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
4
I have a step in a release that gets the Hosted Agent IP address in powershell with:
Invoke-RestMethod http://ipinfo.io/json | Select -exp ip
Hope that helps.
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
For an Ubuntu based VM this is the equivalent command for e.g. a step as a bash script:curl -s http://ipinfo.io/json | jq '.ip', then you can compare the IP address with the CIDR ranges in the XML file at microsoft.com/en-nz/download/details.aspx?id=41653 (be aware it changes weekly, as stated in the other answer). Does anyone know if there is a config/setting page on AzureDevops to know this information without running commands?
– TPPZ
Jan 29 at 11:04
@TPPZ You, me and everybody else is suffering from the same problem. There used to be an API-call (beta/labs) to get agent information, but it has been dropped. Eye-balling the API-docs don't reveal anything useful.
– Jari Turkia
Mar 4 at 11:41
@JariTurkia if it can help with this pain: whatever thing is on Azure that needs to be accessed by the hosted VM on AzureDevOps e.g. a database can have a firewall rule that allows0.0.0.0(cf. docs.microsoft.com/en-us/rest/api/sql/firewallrules/…). This is some sort of special wildcard in the Azure land to avoid updating IPs due to that XML list I was mentioning. In my scenario my Azure DevOps pipeline with the hosted VM was supposed to create/access a SQL Server instance on Azure. When adding the firewall rule in the SQL Server definition, then all good
– TPPZ
Mar 4 at 15:21
add a comment |
4
I have a step in a release that gets the Hosted Agent IP address in powershell with:
Invoke-RestMethod http://ipinfo.io/json | Select -exp ip
Hope that helps.
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
For an Ubuntu based VM this is the equivalent command for e.g. a step as a bash script:curl -s http://ipinfo.io/json | jq '.ip', then you can compare the IP address with the CIDR ranges in the XML file at microsoft.com/en-nz/download/details.aspx?id=41653 (be aware it changes weekly, as stated in the other answer). Does anyone know if there is a config/setting page on AzureDevops to know this information without running commands?
– TPPZ
Jan 29 at 11:04
@TPPZ You, me and everybody else is suffering from the same problem. There used to be an API-call (beta/labs) to get agent information, but it has been dropped. Eye-balling the API-docs don't reveal anything useful.
– Jari Turkia
Mar 4 at 11:41
@JariTurkia if it can help with this pain: whatever thing is on Azure that needs to be accessed by the hosted VM on AzureDevOps e.g. a database can have a firewall rule that allows0.0.0.0(cf. docs.microsoft.com/en-us/rest/api/sql/firewallrules/…). This is some sort of special wildcard in the Azure land to avoid updating IPs due to that XML list I was mentioning. In my scenario my Azure DevOps pipeline with the hosted VM was supposed to create/access a SQL Server instance on Azure. When adding the firewall rule in the SQL Server definition, then all good
– TPPZ
Mar 4 at 15:21
add a comment |
4
4
4
I have a step in a release that gets the Hosted Agent IP address in powershell with:
Invoke-RestMethod http://ipinfo.io/json | Select -exp ip
Hope that helps.
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
I have a step in a release that gets the Hosted Agent IP address in powershell with:
Invoke-RestMethod http://ipinfo.io/json | Select -exp ip
Hope that helps.
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
answered Jan 9 at 1:50
David NiwczykDavid Niwczyk
413
413
For an Ubuntu based VM this is the equivalent command for e.g. a step as a bash script:curl -s http://ipinfo.io/json | jq '.ip', then you can compare the IP address with the CIDR ranges in the XML file at microsoft.com/en-nz/download/details.aspx?id=41653 (be aware it changes weekly, as stated in the other answer). Does anyone know if there is a config/setting page on AzureDevops to know this information without running commands?
– TPPZ
Jan 29 at 11:04
@TPPZ You, me and everybody else is suffering from the same problem. There used to be an API-call (beta/labs) to get agent information, but it has been dropped. Eye-balling the API-docs don't reveal anything useful.
– Jari Turkia
Mar 4 at 11:41
@JariTurkia if it can help with this pain: whatever thing is on Azure that needs to be accessed by the hosted VM on AzureDevOps e.g. a database can have a firewall rule that allows0.0.0.0(cf. docs.microsoft.com/en-us/rest/api/sql/firewallrules/…). This is some sort of special wildcard in the Azure land to avoid updating IPs due to that XML list I was mentioning. In my scenario my Azure DevOps pipeline with the hosted VM was supposed to create/access a SQL Server instance on Azure. When adding the firewall rule in the SQL Server definition, then all good
– TPPZ
Mar 4 at 15:21
add a comment |
For an Ubuntu based VM this is the equivalent command for e.g. a step as a bash script:curl -s http://ipinfo.io/json | jq '.ip', then you can compare the IP address with the CIDR ranges in the XML file at microsoft.com/en-nz/download/details.aspx?id=41653 (be aware it changes weekly, as stated in the other answer). Does anyone know if there is a config/setting page on AzureDevops to know this information without running commands?
– TPPZ
Jan 29 at 11:04
@TPPZ You, me and everybody else is suffering from the same problem. There used to be an API-call (beta/labs) to get agent information, but it has been dropped. Eye-balling the API-docs don't reveal anything useful.
– Jari Turkia
Mar 4 at 11:41
@JariTurkia if it can help with this pain: whatever thing is on Azure that needs to be accessed by the hosted VM on AzureDevOps e.g. a database can have a firewall rule that allows0.0.0.0(cf. docs.microsoft.com/en-us/rest/api/sql/firewallrules/…). This is some sort of special wildcard in the Azure land to avoid updating IPs due to that XML list I was mentioning. In my scenario my Azure DevOps pipeline with the hosted VM was supposed to create/access a SQL Server instance on Azure. When adding the firewall rule in the SQL Server definition, then all good
– TPPZ
Mar 4 at 15:21
For an Ubuntu based VM this is the equivalent command for e.g. a step as a bash script:
curl -s http://ipinfo.io/json | jq '.ip', then you can compare the IP address with the CIDR ranges in the XML file at microsoft.com/en-nz/download/details.aspx?id=41653 (be aware it changes weekly, as stated in the other answer). Does anyone know if there is a config/setting page on AzureDevops to know this information without running commands?– TPPZ
Jan 29 at 11:04
For an Ubuntu based VM this is the equivalent command for e.g. a step as a bash script:
curl -s http://ipinfo.io/json | jq '.ip', then you can compare the IP address with the CIDR ranges in the XML file at microsoft.com/en-nz/download/details.aspx?id=41653 (be aware it changes weekly, as stated in the other answer). Does anyone know if there is a config/setting page on AzureDevops to know this information without running commands?– TPPZ
Jan 29 at 11:04
@TPPZ You, me and everybody else is suffering from the same problem. There used to be an API-call (beta/labs) to get agent information, but it has been dropped. Eye-balling the API-docs don't reveal anything useful.
– Jari Turkia
Mar 4 at 11:41
@TPPZ You, me and everybody else is suffering from the same problem. There used to be an API-call (beta/labs) to get agent information, but it has been dropped. Eye-balling the API-docs don't reveal anything useful.
– Jari Turkia
Mar 4 at 11:41
@JariTurkia if it can help with this pain: whatever thing is on Azure that needs to be accessed by the hosted VM on AzureDevOps e.g. a database can have a firewall rule that allows
0.0.0.0 (cf. docs.microsoft.com/en-us/rest/api/sql/firewallrules/…). This is some sort of special wildcard in the Azure land to avoid updating IPs due to that XML list I was mentioning. In my scenario my Azure DevOps pipeline with the hosted VM was supposed to create/access a SQL Server instance on Azure. When adding the firewall rule in the SQL Server definition, then all good– TPPZ
Mar 4 at 15:21
@JariTurkia if it can help with this pain: whatever thing is on Azure that needs to be accessed by the hosted VM on AzureDevOps e.g. a database can have a firewall rule that allows
0.0.0.0 (cf. docs.microsoft.com/en-us/rest/api/sql/firewallrules/…). This is some sort of special wildcard in the Azure land to avoid updating IPs due to that XML list I was mentioning. In my scenario my Azure DevOps pipeline with the hosted VM was supposed to create/access a SQL Server instance on Azure. When adding the firewall rule in the SQL Server definition, then all good– TPPZ
Mar 4 at 15:21
add a comment |
1
We need to white list the IP address used by the Azure Datacenters in the list mentioned below:
https://www.microsoft.com/en-nz/download/details.aspx?id=41653
Note: This list gets updated every week, so please be mindful of this during the deployment planning
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
If you need to white list these IPs in the firewall rules for other Azure services, then you could just use the work around of start/stop IP range0.0.0.0as explained here: docs.microsoft.com/en-us/rest/api/sql/firewallrules/… this way you don't need to update the IP list according to the XML downloaded weekly from microsoft.com/en-nz/download/details.aspx?id=41653
– TPPZ
Jan 29 at 11:39
add a comment |
1
We need to white list the IP address used by the Azure Datacenters in the list mentioned below:
https://www.microsoft.com/en-nz/download/details.aspx?id=41653
Note: This list gets updated every week, so please be mindful of this during the deployment planning
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
If you need to white list these IPs in the firewall rules for other Azure services, then you could just use the work around of start/stop IP range0.0.0.0as explained here: docs.microsoft.com/en-us/rest/api/sql/firewallrules/… this way you don't need to update the IP list according to the XML downloaded weekly from microsoft.com/en-nz/download/details.aspx?id=41653
– TPPZ
Jan 29 at 11:39
add a comment |
1
1
1
We need to white list the IP address used by the Azure Datacenters in the list mentioned below:
https://www.microsoft.com/en-nz/download/details.aspx?id=41653
Note: This list gets updated every week, so please be mindful of this during the deployment planning
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
We need to white list the IP address used by the Azure Datacenters in the list mentioned below:
https://www.microsoft.com/en-nz/download/details.aspx?id=41653
Note: This list gets updated every week, so please be mindful of this during the deployment planning
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
answered Nov 26 '18 at 22:56
Gagan Jeet SinghGagan Jeet Singh
316
316
If you need to white list these IPs in the firewall rules for other Azure services, then you could just use the work around of start/stop IP range0.0.0.0as explained here: docs.microsoft.com/en-us/rest/api/sql/firewallrules/… this way you don't need to update the IP list according to the XML downloaded weekly from microsoft.com/en-nz/download/details.aspx?id=41653
– TPPZ
Jan 29 at 11:39
add a comment |
If you need to white list these IPs in the firewall rules for other Azure services, then you could just use the work around of start/stop IP range0.0.0.0as explained here: docs.microsoft.com/en-us/rest/api/sql/firewallrules/… this way you don't need to update the IP list according to the XML downloaded weekly from microsoft.com/en-nz/download/details.aspx?id=41653
– TPPZ
Jan 29 at 11:39
If you need to white list these IPs in the firewall rules for other Azure services, then you could just use the work around of start/stop IP range
0.0.0.0 as explained here: docs.microsoft.com/en-us/rest/api/sql/firewallrules/… this way you don't need to update the IP list according to the XML downloaded weekly from microsoft.com/en-nz/download/details.aspx?id=41653– TPPZ
Jan 29 at 11:39
If you need to white list these IPs in the firewall rules for other Azure services, then you could just use the work around of start/stop IP range
0.0.0.0 as explained here: docs.microsoft.com/en-us/rest/api/sql/firewallrules/… this way you don't need to update the IP list according to the XML downloaded weekly from microsoft.com/en-nz/download/details.aspx?id=41653– TPPZ
Jan 29 at 11:39
add a comment |
0
Use a script step in the pipeline to get the current external ip and whitelist it. after pipeline finishes use another script step to clean up.
Thats the only way (for hosted agent), unfortunately.
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
There is an article article around the IP ranges for VSTS/AzureDevOps used by the Microsoft Azure Datacenters (microsoft.com/en-nz/download/details.aspx?id=41653) which change every week. There is a PublicIP xml file for each region which we need to whitelist during any deployment
– Gagan Jeet Singh
Nov 26 '18 at 22:54
this is a real overkill
– 4c74356b41
Nov 27 '18 at 4:42
Thanks for the update and help. The above answer might not work as the customer has to know the IP address up-front in order to White list this. Getting the IP address from the script and then wait for the customer to add it to the White List will not work. So white listing the IP range worked for us.
– Gagan Jeet Singh
Nov 28 '18 at 21:37
might as well whitelist 0.0.0.0
– 4c74356b41
Nov 29 '18 at 5:36
add a comment |
0
Use a script step in the pipeline to get the current external ip and whitelist it. after pipeline finishes use another script step to clean up.
Thats the only way (for hosted agent), unfortunately.
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
There is an article article around the IP ranges for VSTS/AzureDevOps used by the Microsoft Azure Datacenters (microsoft.com/en-nz/download/details.aspx?id=41653) which change every week. There is a PublicIP xml file for each region which we need to whitelist during any deployment
– Gagan Jeet Singh
Nov 26 '18 at 22:54
this is a real overkill
– 4c74356b41
Nov 27 '18 at 4:42
Thanks for the update and help. The above answer might not work as the customer has to know the IP address up-front in order to White list this. Getting the IP address from the script and then wait for the customer to add it to the White List will not work. So white listing the IP range worked for us.
– Gagan Jeet Singh
Nov 28 '18 at 21:37
might as well whitelist 0.0.0.0
– 4c74356b41
Nov 29 '18 at 5:36
add a comment |
0
0
0
Use a script step in the pipeline to get the current external ip and whitelist it. after pipeline finishes use another script step to clean up.
Thats the only way (for hosted agent), unfortunately.
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
Use a script step in the pipeline to get the current external ip and whitelist it. after pipeline finishes use another script step to clean up.
Thats the only way (for hosted agent), unfortunately.
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
answered Nov 22 '18 at 6:10
4c74356b414c74356b41
32.5k42557
32.5k42557
There is an article article around the IP ranges for VSTS/AzureDevOps used by the Microsoft Azure Datacenters (microsoft.com/en-nz/download/details.aspx?id=41653) which change every week. There is a PublicIP xml file for each region which we need to whitelist during any deployment
– Gagan Jeet Singh
Nov 26 '18 at 22:54
this is a real overkill
– 4c74356b41
Nov 27 '18 at 4:42
Thanks for the update and help. The above answer might not work as the customer has to know the IP address up-front in order to White list this. Getting the IP address from the script and then wait for the customer to add it to the White List will not work. So white listing the IP range worked for us.
– Gagan Jeet Singh
Nov 28 '18 at 21:37
might as well whitelist 0.0.0.0
– 4c74356b41
Nov 29 '18 at 5:36
add a comment |
There is an article article around the IP ranges for VSTS/AzureDevOps used by the Microsoft Azure Datacenters (microsoft.com/en-nz/download/details.aspx?id=41653) which change every week. There is a PublicIP xml file for each region which we need to whitelist during any deployment
– Gagan Jeet Singh
Nov 26 '18 at 22:54
this is a real overkill
– 4c74356b41
Nov 27 '18 at 4:42
Thanks for the update and help. The above answer might not work as the customer has to know the IP address up-front in order to White list this. Getting the IP address from the script and then wait for the customer to add it to the White List will not work. So white listing the IP range worked for us.
– Gagan Jeet Singh
Nov 28 '18 at 21:37
might as well whitelist 0.0.0.0
– 4c74356b41
Nov 29 '18 at 5:36
There is an article article around the IP ranges for VSTS/AzureDevOps used by the Microsoft Azure Datacenters (microsoft.com/en-nz/download/details.aspx?id=41653) which change every week. There is a PublicIP xml file for each region which we need to whitelist during any deployment
– Gagan Jeet Singh
Nov 26 '18 at 22:54
There is an article article around the IP ranges for VSTS/AzureDevOps used by the Microsoft Azure Datacenters (microsoft.com/en-nz/download/details.aspx?id=41653) which change every week. There is a PublicIP xml file for each region which we need to whitelist during any deployment
– Gagan Jeet Singh
Nov 26 '18 at 22:54
this is a real overkill
– 4c74356b41
Nov 27 '18 at 4:42
this is a real overkill
– 4c74356b41
Nov 27 '18 at 4:42
Thanks for the update and help. The above answer might not work as the customer has to know the IP address up-front in order to White list this. Getting the IP address from the script and then wait for the customer to add it to the White List will not work. So white listing the IP range worked for us.
– Gagan Jeet Singh
Nov 28 '18 at 21:37
Thanks for the update and help. The above answer might not work as the customer has to know the IP address up-front in order to White list this. Getting the IP address from the script and then wait for the customer to add it to the White List will not work. So white listing the IP range worked for us.
– Gagan Jeet Singh
Nov 28 '18 at 21:37
might as well whitelist 0.0.0.0
– 4c74356b41
Nov 29 '18 at 5:36
might as well whitelist 0.0.0.0
– 4c74356b41
Nov 29 '18 at 5:36
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422395%2fhow-to-get-the-ip-address-for-azure-devops-hosted-agents-to-add-to-the-white-lis%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
