Elastic Cloud is available as an offering through the Azure console.

Prerequisites

There are a few requirements to check before setting up an Elastic Cloud deployment:

Getting started

Access Elastic Cloud from Azure in two ways:

When you create an Elastic Cloud deployment, an Elastic Stack cluster is created for you. The size of this deployment is 16GB of RAM and 560GB of storage, across two availability zones for redundancy. The size of the deployment, both RAM and storage, is changed directly in the Elastic console. Usage charges are based on the deployment size, so size your instance efficiently. The deployment defaults to the latest available version of the Elastic Stack. Check our Version policy to learn more about when new versions are made available and old versions are removed from service.

Pricing is pay-as-you-go per hour for each Elastic Cloud deployment created. Note that there is no free trial period for the offering. Charges are applied to your Azure bill at the end of the month. Use the Elastic Cloud Pricing Calculator to size a deployment and view the corresponding hourly rate.

Elastic charges include:

Modify your subscription level on the billing page in the Elastic console.

No. Elastic is not currently integrated with Azure user management. Azure users who deploy Elasticsearch on Azure view and manage their own cluster through the Cloud console. Other Azure users in the same tenant cannot access clusters through the Cloud console other than those that they themselves created.

When trying to access resources such as Elasticsearch, Kibana, Enterprise Search, or APM in a deployment that was created by another Azure user, the following error is shown:

Share deployment resources directly with other Azure users by configuring Active Directory single sign-on with the Elasticsearch cluster.

Yes. You can start a free Elasticsearch Service trial and then convert your account over to Azure. There are a few requirements:

After you subscribe to Elastic Cloud through the Azure Native ISV Service, Elastic has access to the following Azure tenant information:

Elastic can also access data from Elastic Cloud Azure Native ISV Service features, including resource and activity log data. This data is available to Elastic only if you enable it. By default, Elastic does not have access to this information.

Use any of the following methods:

First create a new account configured with Elastic Cloud Azure Native ISV Service, then perform the migration as follows:

The way Azure Marketplace Billing Integration works today, the costs for Elastic resources (deployments) are reported for an Elastic Cloud organization as a single line item, reported against the Marketplace SaaS ID. This includes the Elastic deployments created using the Azure Portal, API, SDK, or CLI, and also the Elastic deployments created directly from the Elasticsearch Service Console in the respective Elastic Cloud organization. For granular Elastic resources costs refer to Monitor and analyze your acccount usage. As well, for more detail refer to Integrated billing.

With Elastic Cloud Azure Native ISV Service, the "instance name/ID" shown in the Azure Marketplace invoice is the Azure Marketplace SaaS identifier that represents an Elastic Cloud organization. For Microsoft Azure, Microsoft.SaaS (namespace) resources are used for billing Marketplace Resources - in this case, Elastic.

For instance: Elastic Organization Org1 is associated with a Marketplace SaaS (Microsoft.SaaS) asset AzureElastic_GUID_NAME. The Elastic resources (Microsoft.Elastic) E1, E2, and E3 within Org1 are all mapped to AzureElastic_GUID_NAME.

Microsoft.SaaS (Instance name) asset is shown in the Azure Marketplace invoice and represents costs related to an Elastic Cloud organization and not individual Elastic resources (deployments). To see the cost breakdown for individual Elastic resources (deployments), refer to Monitor and analyze your acccount usage.

Each Elastic Cloud deployment includes:

Navigate to the deployment overview page in Azure:

Modify your Elastic Cloud deployment in the Elastic Cloud console, which is accessed from the Azure UI through the Advanced Settings link on the deployment overview page. In the Elastic Cloud console you can perform a number of actions against your deployment, including:

The Elastic Cloud Azure Native ISV Service simplifies logging for Azure services with the Elastic Stack. This integration supports:

You can monitor your Azure virtual machines by installing the Elastic Agent VM extension. Once enabled, the VM extension downloads the Elastic Agent, installs it, and enrols it to the Fleet Server. The Elastic Agent will then send system related logs and metrics to the Elastic Cloud cluster where you can find pre-built system dashboards showing the health and performance of your virtual machines.

Enabling and disabling VM extensions

To enable or disable a VM extension:

While it’s possible to enable or disable a VM extension directly from the VM itself, we recommend always enabling or disabling your Elasticsearch VM extensions from within the context of your Elasticsearch deployment.

Managing the Elastic Agent VM extension

Once installed on the virtual machine, you can manage Elastic Agent either from Fleet or locally on the host where it’s installed. We recommend managing the VM extension through Fleet, because it makes handling and upgrading the agents considerably easier. For more information on the Elastic Agent, check Manage your Elastic Agents.

Operating system compatibility matrix

The Azure Elastic Agent VM extension is supported on the following operating systems:

When trying to access Elastic Cloud resources, you may get an error message indicating that the user must have the required authorization.

Elastic is not currently integrated with Azure user management, so sharing deployment resources through the Cloud console with other Azure users is not possible. However, sharing direct access to these resources is possible. For details, check Is the Elastic Cloud Azure Native ISV Service connected with Azure user management?.

When creating a new Elastic Cloud deployment, the deployment creation may fail with a Your deployment failed error. The process results with a status message such as:

{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "500",
      "message": "An error occurred during deployment creation. Please try again. If the problem persists, please contact support@elastic.co."
    }
  ]

One possible cause of a deployment creation failure is the default traffic filtering rules. Deployments fail to create if a previously created traffic filter has enabled the Include by default option. When this option is enabled, traffic to the deployment is blocked, including traffic that is part of the Elastic Cloud Azure Native ISV Service. As a result, some of the integration components are not successfully provisioned and the deployment creation fails.

Follow these steps to resolve the problem:

When you try to access your Elastic Cloud deployment using single sign-on, the access may fail due to missing permission required by your Azure environment.

You can review your user consent settings configuration following the instructions in Configure how users consent to applications. To resolve this problem, contact your Azure Administrator.

Support is provided by Elastic. To open a support case:

In case your Elastic Cloud resource is not fully set up and you’re not able to access the Support page, you can always send an email to support@elastic.co.