Security Center: Security Allowed Connections
API spec for Microsoft.Security (Azure Security Center) resource provider
Identity & security#openapi#cloud
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
API spec for Microsoft.Security (Azure Security Center) resource provider
Endpoints 3
AllowedConnections
- GETAllowedConnections_List
/subscriptions/:subscriptionId/providers/Microsoft.Security/allowedConnections?api-version=stringGets the list of all possible traffic between resources for the subscription - GETAllowedConnections_ListByHomeRegion
/subscriptions/:subscriptionId/providers/Microsoft.Security/locations/:ascLocation/allowedConnections?api-version=stringGets the list of all possible traffic between resources for the subscription and location. - GETAllowedConnections_Get
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Security/locations/:ascLocation/allowedConnections/:connectionType?api-version=stringGets the list of all possible traffic between resources for the subscription and location, based on connection type.
API details
- Base URL
https://management.azure.com- Authentication
- OAuth 2.0 (implicit flow) with 1 scope
- Operations
- 3 operations on 3 pathsGET 3
- Main resources
- AllowedConnections 3
- Response formats
application/json- Description format
- Swagger 2.0, API version
2015-06-01-preview - Links
- OpenAPI document
- Listed from
- APIs.guru OpenAPI Directory (CC0-1.0)
Source updated
How to test the Security Center: Security Allowed Connections in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Security Center: Security Allowed Connections collection, without the publisher's secrets.
- Add your credentialsThis API uses OAuth 2.0 (implicit flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “AllowedConnections_List” (GET /subscriptions/:subscriptionId/providers/Microsoft.Security/allowedConnections?api-version=string), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Security Center: Security Allowed Connections?
API spec for Microsoft.Security (Azure Security Center) resource provider It is listed under Identity & security and has 3 endpoints.
Who publishes the Security Center: Security Allowed Connections?
It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Security Center: Security Allowed Connections?
Requests go to https://management.azure.com. Endpoint paths are added to this base URL.
How do I authenticate with the Security Center: Security Allowed Connections?
With OAuth 2.0 (implicit flow) with 1 scope.
How many endpoints does the Security Center: Security Allowed Connections have?
3 operations on 3 paths (3 GET). The largest groups are AllowedConnections.
Is forking the Security Center: Security Allowed Connections free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.