{"id":2300,"date":"2023-08-07T04:00:41","date_gmt":"2023-08-07T11:00:41","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/azure-sql\/?p=2300"},"modified":"2023-08-04T15:10:29","modified_gmt":"2023-08-04T22:10:29","slug":"summer-2023-update-for-azure-sql-db-external-rest-endpoint-invocation","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/azure-sql\/summer-2023-update-for-azure-sql-db-external-rest-endpoint-invocation\/","title":{"rendered":"Summer 2023 Update for Azure SQL Database External REST Endpoint Invocation"},"content":{"rendered":"

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

Summer 2023 REST Endpoint Invocation Update<\/h2>\n

Welcome to the Summer 2023 REST Endpoint Invocation update post! This summer, we updated the External REST Endpoints Invocation <\/strong>feature with a few key fixes and additions to help you use more Azure Services with your Azure SQL Database. The feature was released to public preview last year<\/a> and this latest set of new features are preparing it for General Availability in the near future.<\/p>\n

As a refresher, this feature makes it possible to call REST endpoints from other Azure Services from right in the Azure SQL Database. With a quick call to the system stored procedure sp_invoke_external_rest_endpoint<\/span><\/strong>, you can have data processed via an Azure Function, update a PowerBI dashboard, or even talk to OpenAI. Here is a quick example of sending a REST request to an Azure Function:<\/p>\n

DECLARE @ret INT, @response NVARCHAR(MAX);\r\n\r\nEXEC @ret = sp_invoke_external_rest_endpoint\r\n \u00a0 \u00a0 @url = N'https:\/\/mydemofunction.azurewebsites.net\/api\/HttpTrigger',\r\n \u00a0 \u00a0 @payload = N'{\"name\":\"test\"}',\r\n \u00a0 \u00a0 @method = N'POST',\r\n \u00a0 \u00a0 @response = @response OUTPUT;\r\n\r\nSELECT @ret AS ReturnCode, @response AS Response;<\/pre>\n
Very straightforward and easy to use.<\/p>\n
What’s New for Summer 2023<\/h2>\n
More Azure Services<\/h2>\n
To start, we have expanded on the Azure Services you can call, adding OpenAI, Azure Blob Storage, Azure Files, Azure Queue Services and Azure Table Services.<\/p>\n
The full list is as follows:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Azure Service<\/th>\nDomain<\/th>\n<\/tr>\n<\/thead>\n
Azure Functions<\/td>\n*.azurewebsites.net<\/td>\n<\/tr>\n
Azure Apps Service<\/td>\n*.azurewebsites.net<\/td>\n<\/tr>\n
Azure App Service Environment<\/td>\n*.appserviceenvironment.net<\/td>\n<\/tr>\n
Azure Static Web Apps<\/td>\n*.azurestaticapps.net<\/td>\n<\/tr>\n
Azure Logic Apps<\/td>\n*.logic.azure.com<\/td>\n<\/tr>\n
Azure Event Hubs<\/td>\n*.servicebus.windows.net<\/td>\n<\/tr>\n
Azure Event Grid<\/td>\n*.eventgrid.azure.net<\/td>\n<\/tr>\n
Azure Cognitive Services<\/td>\n*.cognitiveservices.azure.com<\/td>\n<\/tr>\n
PowerApps \/ Dataverse<\/td>\n*.api.crm.dynamics.com<\/td>\n<\/tr>\n
Microsoft Dynamics<\/td>\n*.dynamics.com<\/td>\n<\/tr>\n
Azure Container Instances<\/td>\n*.azurecontainer.io<\/td>\n<\/tr>\n
Azure Container Apps<\/td>\n*.azurecontainerapps.io<\/td>\n<\/tr>\n
Power BI<\/td>\napi.powerbi.com<\/td>\n<\/tr>\n
Microsoft Graph<\/td>\ngraph.microsoft.com<\/td>\n<\/tr>\n
Analysis Services<\/td>\n*.asazure.windows.net<\/td>\n<\/tr>\n
IoT Central<\/td>\n*.azureiotcentral.com<\/td>\n<\/tr>\n
API Management<\/td>\n*.azure-api.net<\/td>\n<\/tr>\n
Azure OpenAI<\/strong><\/td>\n*.openai.azure.com<\/strong><\/td>\n<\/tr>\n
Azure Blob Storage<\/strong><\/td>\n*.blob.core.windows.net<\/strong><\/td>\n<\/tr>\n
Azure Files<\/strong><\/td>\n*.file.core.windows.net<\/strong><\/td>\n<\/tr>\n
Azure Queue Storage<\/strong><\/td>\n*.queue.core.windows.net<\/strong><\/td>\n<\/tr>\n
Azure Table Storage<\/strong><\/td>\n*.table.core.windows.net<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
XML and Text Payloads<\/h2>\n
Expanding on core functionality, we have added the ability to have request and response payloads <\/span><\/span>be text or XML. You can now use the following media types for the header\u00a0content-type:<\/em><\/strong><\/p>\n