{"id":1402,"date":"2022-11-16T06:00:28","date_gmt":"2022-11-16T14:00:28","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/azure-sql\/?p=1402"},"modified":"2022-11-16T06:15:48","modified_gmt":"2022-11-16T14:15:48","slug":"azure-sql-database-external-rest-endpoints-integration-public-preview","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/azure-sql\/azure-sql-database-external-rest-endpoints-integration-public-preview\/","title":{"rendered":"Azure SQL Database External REST Endpoints Integration Public Preview"},"content":{"rendered":"

\"Image<\/a><\/p>\n

The ability to call a REST endpoint natively from Azure SQL Database<\/strong>, which was made available via an Early Adopter Preview in May, is now moving to Public Preview<\/strong>. I’m extremely happy that as of today the new system stored procedure sp_invoke_external_rest_endpoint<\/code> is available to everyone, automatically and transparently: you can use it right away, from any Azure SQL Database that you may already have or that you’ll create in future<\/strong>.<\/p>\n

With sp_invoke_external_rest_endpoint<\/code> you can call a REST endpoint, like an Azure Function, for example, with just a line of code:<\/p>\n

declare @ret as int, @response as nvarchar(max);\r\n\r\nexec @ret = sp_invoke_external_rest_endpoint \r\n\t@method = 'GET',\r\n\t@url = 'https:\/\/my-function.azurewebsites.net\/api\/say?message=hello world',\r\n\t@response = @response output;\r\n\t\r\nselect @ret as ReturnCode, @response as Response;<\/pre>\n
Here’s a screenshot of the result of calling an Azure Function that provides information about local restaurants. The screenshot also shows that you can also query using GraphQL, if that is supported by the called endpoint.<\/p>\n
\"sp_invoke_external_rest_endpoint<\/a><\/p>\n
Azure Function is just one of the services you can use with sp_invoke_external_rest_endpoint<\/code>. In fact, you can call any<\/strong> of the following Azure services:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
Azure Service<\/th>\n<\/tr>\n<\/thead>\n
Azure Functions<\/td>\nAzure Apps Service<\/td>\n<\/tr>\n
Azure App Service Environment<\/td>\nAzure Static Web Apps<\/td>\n<\/tr>\n
Azure Logic Apps<\/td>\nAzure Container Instances<\/td>\n<\/tr>\n
Azure Event Grid<\/td>\nAzure Event Hubs<\/td>\n<\/tr>\n
PowerApps \/ Dataverse<\/td>\nAzure Cognitive Services<\/td>\n<\/tr>\n
Power BI<\/td>\nMicrosoft Graph<\/td>\n<\/tr>\n
Analysis Services<\/td>\nIoT Central<\/td>\n<\/tr>\n
API Management<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Aside from calling an Azure Function, as you can see, you really have a lot of options which will enable you to create more user-friendly and responsive solutions. Just a few ideas, for example:<\/p>\n