Microsoft Azure

Azure SQL: Network Security Perimeter Configurations

The Azure SQL Database management API provides a RESTful set of web APIs that interact with Azure SQL Database services to manage your databases. The API…

Identity & security#openapi

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

The Azure SQL Database management API provides a RESTful set of web APIs that interact with Azure SQL Database services to manage your databases. The API enables users to create, retrieve, update, and delete databases, servers, and other entities.

Endpoints 3

NetworkSecurityPerimeterConfigurations

  • GETNetworkSecurityPerimeterConfigurations_ListByServer/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Sql/servers/:serverName/networkSecurityPerimeterConfigurationsGets a list of NSP configurations for a server.
  • GETNetworkSecurityPerimeterConfigurations_Get/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Sql/servers/:serverName/networkSecurityPerimeterConfigurations/:nspConfigNameGets a network security perimeter configuration.
  • POSTNetworkSecurityPerimeterConfigurations_Reconcile/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Sql/servers/:serverName/networkSecurityPerimeterConfigurations/:nspConfigName/reconcileReconcile network security perimeter configuration for SQL Resource Provider

API details

Base URL
https://management.azure.com
Authentication
OAuth 2.0 (implicit flow) with 1 scope
Operations
3 operations on 3 pathsGET 2POST 1
Main resources
NetworkSecurityPerimeterConfigurations 3
Response formats
application/json
Description format
Swagger 2.0, API version 2025-01-01

How to test the Azure SQL: Network Security Perimeter Configurations in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Azure SQL: Network Security Perimeter Configurations collection, without the publisher's secrets.
  3. 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.
  4. Send a requestPick an endpoint, for example “NetworkSecurityPerimeterConfigurations_ListByServer” (GET /subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Sql/servers/:serverName/networkSecurityPerimeterConfigurations), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Azure SQL: Network Security Perimeter Configurations?

The Azure SQL Database management API provides a RESTful set of web APIs that interact with Azure SQL Database services to manage your databases. The API… It is listed under Identity & security and has 3 endpoints.

Who publishes the Azure SQL: Network Security Perimeter Configurations?

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 Azure SQL: Network Security Perimeter Configurations?

Requests go to https://management.azure.com. Endpoint paths are added to this base URL.

How do I authenticate with the Azure SQL: Network Security Perimeter Configurations?

With OAuth 2.0 (implicit flow) with 1 scope.

How many endpoints does the Azure SQL: Network Security Perimeter Configurations have?

3 operations on 3 paths (2 GET, 1 POST). The largest groups are NetworkSecurityPerimeterConfigurations.

Is forking the Azure SQL: Network Security Perimeter Configurations free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.