Forum Discussion
Solved
API v4, Microsoft Azure using connections vs. connections/bulk
Hello Equinix, I have a question regarding the creation of a new, redundant connection to Azure with API v4. From "Guide to v3-to-v4 APIs Migration" I see that I should use the connections/bulk en...
- Yes, We can make 2 calls to POST- Create connection V4 API.
First, to create primary connections, the response of this call will have the below redundancy group ID.
"redundancy": { "group": "a00cef6f-8e35-4794-9ff9-665e084e4e6d" }
Second to create a Secondary connection, while creating this one, use the redundancy group ID that is received from the first connection response.
Yes, We can make 2 calls to POST- Create connection V4 API.
First, to create primary connections, the response of this call will have the below redundancy group ID.
"redundancy": { "group": "a00cef6f-8e35-4794-9ff9-665e084e4e6d" }
Second to create a Secondary connection, while creating this one, use the redundancy group ID that is received from the first connection response.
First, to create primary connections, the response of this call will have the below redundancy group ID.
"redundancy": { "group": "a00cef6f-8e35-4794-9ff9-665e084e4e6d" }
Second to create a Secondary connection, while creating this one, use the redundancy group ID that is received from the first connection response.
