Get Virtual Network Data

You can get data on a virtual network with the specified ID.

Request

To retrieve information on a specific virtual network, send the HTTP GET request to the /virtualNetworks/{networkId} endpoint. {networkId} is a system ID assigned to the virtual network in the Veeam Backup for Microsoft Azure REST API.

HTTP Request

GET https://<hostname>/api/v2/cloudInfrastructure/virtualNetworks/{networkId}

Request Headers

The request contains the following headers.

Header

Required

Value

Description

Authorization

Required

Bearer <Access-Token>

Authenticates a client who sends the request to the server. Must contain the access token for the current logon session in the Bearer <Access-Token> format.

Response

The server returns the following response to the client.

Response Codes

A successfully completed operation returns a response code 200 (OK).

Response Headers

The response to this request contains the following headers. The response may also include additional standard HTTP headers.

Header

Value

Description

Content-length

integer

Identifies the length of the response body message, in bytes.

Content-type

  • application/json
  • application/problem+json

Identifies the media type of the response body message.

Response Body

In the response body, Veeam Backup for Microsoft Azure returns a representation of the virtual network with the specified ID. The VirtualNetworkV2 schema is used for the resource representation.

Get Virtual Network DataExample

The following request returns information on a vitrual network with the ID /subscriptions/1142bdc7-8797-42bc-aa23-9f1fc1411946/resourcegroups/tc-integrationtests-infrastructure/providers/microsoft.network/virtualnetworks/0bccde1d-7a37-487d-9178-c776a9624898",  "name": "0bccde1d-7a37-487d-9178-c776a9624898.

Request:

GET https://51.11.247.127/api/v2/cloudInfrastructure/virtualNetworks/%2Fsubscriptions%2F1142bdc7-8797-42bc-aa23-9f1fc1411946%2Fresourcegroups%2Ftc-integrationtests-infrastructure%2Fproviders%2Fmicrosoft.network%2Fvirtualnetworks%2F0bccde1d-7a37-487d-9178-c776a9624898

 

Request Header:

Authorization: Bearer <Access-Token>

 

Response:

200

 

Response Body:

{

 "id": "/subscriptions/1142bdc7-8797-42bc-aa23-9f1fc1411946/resourcegroups/tc-integrationtests-infrastructure/providers/microsoft.network/virtualnetworks/0bccde1d-7a37-487d-9178-c776a9624898",

 "name": "0bccde1d-7a37-487d-9178-c776a9624898",

 "regionName": "eastasia",

 "addressSpaces": [

   "10.4.15.0/24"

 ],

 "_links": {

   "subscription": {

     "href": "https://51.11.247.127/api/v2/cloudInfrastructure/subscriptions/1142bdc7-8797-42bc-aa23-9f1fc1411946"

   },

   "self": {

     "href": "https://51.11.247.127/api/v2/cloudInfrastructure/virtualNetworks/%2Fsubscriptions%2F1142bdc7-8797-42bc-aa23-9f1fc1411946%2Fresourcegroups%2Ftc-integrationtests-infrastructure%2Fproviders%2Fmicrosoft.network%2Fvirtualnetworks%2F0bccde1d-7a37-487d-9178-c776a9624898"

   }

 }

}

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.