Elastic Cloud (Elasticsearch) – An Azure native ISV service is co-developed and co-managed by Microsoft and Elastic and enables our joint customers to setup their Elastic deployments right from within the Azure portal for their vector search, observability or security use cases. The service can be seamlessly managed using clients such as Azure portal, Command-line interfaces (CLI) and Software Development Kits (SDKs) without requiring any custom code.
The service has continued to grow and has been widely adopted by our joint customers. Based on your feedback, we continue to invest in deeper integrations to make the experience smoother for you. Here are some of the key features released recently that we would like to highlight:
- Azure OpenAI Connector – Seamlessly create an Azure OpenAI Connector through your native resource and use it in your Elastic observability assistant
- Manage Elastic extension for VMSS (Virtual Machine Scale Sets) – Install the Elastic extension to gather logs and metrics on your VMSS resources across your subscriptions in bulk
- Multi-subscription monitoring – Scalable monitoring of resources across your subscriptions with a single Elastic resource
Azure OpenAI Connector
You can now create an Azure OpenAI connector via the native integration. You can choose to either create one during the Elastic resource creation or post resource creation in the new “Azure OpenAI configuration” blade. This helps you setup your connector without switching contexts between your AOAI resource(in Azure portal) and the Elastic console.
During resource creation, select your Azure OpenAI resource and deployment to create a connector:
Alternatively, to create a connector through an existing resource, click on the Azure OpenAI configuration blade and then click Add.
Select the Azure OpenAI resource and deployment and click Create. Confirm that the Integration Status is “Succeeded”.
The connector, once created, appears in the Kibana Stack Management page:
The connector can be used to configure Elastic’s Observability AI Assistant. Elastic would then invoke the AOAI deployment url for chat completion/text generation tasks.
Learn more about Elastic OpenAI Connectors here.
Manage Elastic Extension for VMSS
You can now install the Elastic agent as an extension on your VMSS resources across your subscriptions. Select the Virtual Machine Scale Sets blade from the Elastic deployment configuration section, select the VMSS resource(s) and click on Install Extension. VMSS resources across all your subscriptions in the tenant are displayed. This extension will allow you to push all your logs and metrics from your VMSS to Elastic’s Observability solution to manage and troubleshoot your Azure workloads
Multi-subscription monitoring
We are excited to announce a scalable multi-subscription monitoring capability that allows you to configure monitoring for all your subscriptions through a single Elastic resource. You no longer need to create new Elastic resource for every subscription that you intend to monitor.
To start monitoring multiple subscriptions through a single Elastic Cloud resource, click on the Monitored Subscriptions blade under the Elastic deployment configuration section.
Click on the “Add subscriptions” button and on the window that opens, select the subscriptions that you want to monitor using the same resource and click Add.
The set of tag rules for logs defined for the Elastic resource apply to all subscriptions that are added for monitoring. If you wish to reconfigure the tag rules at any point, check Reconfigure rules for metrics and logs.
And now you are done. Go to the “Monitored Resources” blade in your Elastic resource and filter the subscription of your choice to check the status of logs being sent to Elastic for the resources in that subscription.
Log forwarder
Elastic's native integration with Azure offers automatic log forwarding out of the box, removing the need for an Elastic Agent and its additional infrastructure, thus saving time. We are continuously expanding support to include all resource categories on Azure Monitor for log shipment to Elastic. For customers who have configured monitoring tag rules in their Azure subscription, new resource types or categories are automatically enrolled to send logs, without requiring any manual adjustments. Currently, this native integration supports log forwarding from over 130 resource types on Azure.
To enable automatic creation of diagnostic settings on your resources and subscription and enable the native log forwarder, enable the same in the Logs & Metrics blade. To configure tag rules for your logs, check Reconfigure rules for metrics and logs.
Next steps
- If you would like to subscribe to the service, check out Elastic Cloud (Elasticsearch) - An Azure Native ISV Service from Azure marketplace.
- To learn more about the service, check out our documentation.
- If you already use Elastic Cloud (Elasticsearch) – An Azure Native ISV Service, and have feedback or feature requests, please share in our feedback forum.
Microsoft
