Azure SQL: Database Security Alert Policies
Provides create, read and update functionality for database Threat Detection policies.
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
Provides create, read and update functionality for database Threat Detection policies.
Endpoints 2
SecurityAlert
- GETDatabaseThreatDetectionPolicies_Get
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Sql/servers/:serverName/databases/:databaseName/securityAlertPolicies/:securityAlertPolicyNameGets a database's threat detection policy. - PUTDatabaseThreatDetectionPolicies_CreateOrUpdate
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Sql/servers/:serverName/databases/:databaseName/securityAlertPolicies/:securityAlertPolicyNameCreates or updates a database's threat detection policy.
API details
- Base URL
https://management.azure.com- Authentication
- OAuth 2.0 (implicit flow) with 1 scope
- Operations
- 2 operations on 1 pathGET 1PUT 1
- Main resources
- SecurityAlert 2
- Response formats
application/json- Description format
- Swagger 2.0, API version
2014-04-01 - Links
- OpenAPI document
How to test the Azure SQL: Database Security Alert Policies 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 Azure SQL: Database Security Alert Policies 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 “DatabaseThreatDetectionPolicies_Get” (GET /subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Sql/servers/:serverName/databases/:databaseName/securityAlertPolicies/:securityAlertPolicyName), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Azure SQL: Database Security Alert Policies?
Provides create, read and update functionality for database Threat Detection policies. It is listed under Identity & security and has 2 endpoints.
Who publishes the Azure SQL: Database Security Alert Policies?
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: Database Security Alert Policies?
Requests go to https://management.azure.com. Endpoint paths are added to this base URL.
How do I authenticate with the Azure SQL: Database Security Alert Policies?
With OAuth 2.0 (implicit flow) with 1 scope.
How many endpoints does the Azure SQL: Database Security Alert Policies have?
2 operations on 1 path (1 GET, 1 PUT). The largest groups are SecurityAlert.
Is forking the Azure SQL: Database Security Alert Policies free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.