From 23c15931d834a683278a7117566dfef845635f42 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Fri, 27 Feb 2026 17:35:00 -0500 Subject: [PATCH 01/19] step 1 --- cloud-account/index.md | 4 +- .../join-or-leave-an-organization.md | 6 +- cloud-account/multifactor-authentication.md | 4 +- cloud-account/switch-organizations.md | 0 cloud-account/update-your-email-address.md | 4 +- deploy-manage/cloud-organization.md | 30 +++++-- deploy-manage/cloud-organization/billing.md | 4 +- .../billing/add-billing-details.md | 4 +- .../cloud-organization/billing/billing-faq.md | 10 +-- .../cloud-organization/delete-organization.md | 0 .../manage-multiple-organizations.md | 90 +++++++++++++++++++ .../cloud-organization/operational-emails.md | 2 +- .../cloud-organization/tools-and-apis.md | 4 + .../elastic-cloud/create-an-organization.md | 20 ++--- .../subscribe-from-marketplace.md | 2 + deploy-manage/users-roles.md | 4 +- .../users-roles/cloud-organization.md | 6 +- .../cloud-organization/manage-users.md | 11 ++- 18 files changed, 158 insertions(+), 47 deletions(-) create mode 100644 cloud-account/switch-organizations.md create mode 100644 deploy-manage/cloud-organization/delete-organization.md create mode 100644 deploy-manage/cloud-organization/manage-multiple-organizations.md diff --git a/cloud-account/index.md b/cloud-account/index.md index ab7fc8ee82..384d6728bd 100644 --- a/cloud-account/index.md +++ b/cloud-account/index.md @@ -3,9 +3,9 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-account-user-settings.html - https://www.elastic.co/guide/en/serverless/current/general-user-profile.html applies_to: - serverless: all + serverless: ga deployment: - ess: all + ess: ga products: - id: cloud-hosted - id: cloud-serverless diff --git a/cloud-account/join-or-leave-an-organization.md b/cloud-account/join-or-leave-an-organization.md index eb3bf14115..700a387e7a 100644 --- a/cloud-account/join-or-leave-an-organization.md +++ b/cloud-account/join-or-leave-an-organization.md @@ -3,14 +3,16 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-invite-users.html - https://www.elastic.co/guide/en/serverless/current/general-manage-organization.html applies_to: - serverless: all + serverless: ga deployment: - ess: all + ess: ga products: - id: cloud-hosted - id: cloud-serverless --- +% EDIT ME! + # Join or leave an organization Organizations in {{ecloud}} group user accounts, projects and deployments under a common billing and access structure. If you have been invited to an organization, you can accept the invitation and become a member. You can also leave an organization at any time, as long as you don’t have active projects or deployments associated with your account. diff --git a/cloud-account/multifactor-authentication.md b/cloud-account/multifactor-authentication.md index 5b67f06875..5814152a49 100644 --- a/cloud-account/multifactor-authentication.md +++ b/cloud-account/multifactor-authentication.md @@ -2,9 +2,9 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-account-security-mfa.html applies_to: - serverless: all + serverless: ga deployment: - ess: all + ess: ga products: - id: cloud-hosted --- diff --git a/cloud-account/switch-organizations.md b/cloud-account/switch-organizations.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/cloud-account/update-your-email-address.md b/cloud-account/update-your-email-address.md index c61b3f7028..b8777883ed 100644 --- a/cloud-account/update-your-email-address.md +++ b/cloud-account/update-your-email-address.md @@ -2,9 +2,9 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-update-email-address.html applies_to: - serverless: all + serverless: ga deployment: - ess: all + ess: ga products: - id: cloud-hosted --- diff --git a/deploy-manage/cloud-organization.md b/deploy-manage/cloud-organization.md index 419ce9fea3..3f22678673 100644 --- a/deploy-manage/cloud-organization.md +++ b/deploy-manage/cloud-organization.md @@ -3,17 +3,23 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-organizations.html applies_to: deployment: - ess: all - serverless: all + ess: ga + serverless: ga products: - id: cloud-hosted --- # Manage your Cloud organization [ec-organizations] -When you [sign up for {{ecloud}}](/deploy-manage/deploy/elastic-cloud/create-an-organization.md), you create an organization. This organization is the umbrella for all of your {{ecloud}} resources, users, and account settings. Every organization has a unique identifier. +An organization is the umbrella for a group of {{ecloud}} resources, users, and account settings. Every organization has a unique identifier. -You can perform the following tasks to manage your Cloud organization: +When you [sign up for {{ecloud}}](/deploy-manage/deploy/elastic-cloud/create-an-organization.md), you have the option to create a new organization. You also can be [added to an existing organization](/deploy-manage/users-roles/cloud-organization/manage-users.md). + +The administrator of an organization is referred to as the organization owner, and belongs to the [Organization owner role](/deploy-manage/users-roles/cloud-organization/user-roles.md#organization-level-roles). An organization can have more than one organization owner. + +## Organization management tasks + +As an organization owner, you can perform the following tasks to manage your Cloud organization: * [Manage billing](/deploy-manage/cloud-organization/billing.md) * Manage user access to your organization: @@ -23,10 +29,24 @@ You can perform the following tasks to manage your Cloud organization: * [Configure SAML single sign-on](/deploy-manage/users-roles/cloud-organization/configure-saml-authentication.md) to your organization * [Manage API keys](/deploy-manage/api-keys.md) to use with the [{{ecloud}}](https://www.elastic.co/docs/api/doc/cloud), [{{ecloud}} Billing](https://www.elastic.co/docs/api/doc/cloud-billing/), and [{{serverless-full}}](https://www.elastic.co/docs/api/doc/elastic-cloud-serverless) APIs * Configure who receives [operational emails](/deploy-manage/cloud-organization/operational-emails.md) related to your organization -* Track the [status of {{ecloud}} services](/deploy-manage/cloud-organization/service-status.md). +* Track the [status of {{ecloud}} services](/deploy-manage/cloud-organization/service-status.md) +* [Delete](/deploy-manage/cloud-organization/delete-an-organization.md) an organization. Several aspects of your organization can also be managed using tools provided by Elastic. For a list of tools, refer to [{{ecloud}} organization tools and APIs](/deploy-manage/cloud-organization/tools-and-apis.md). ::::{tip} To learn how to manage your {{ecloud}} account as a user, refer to [Manage your Cloud account](/cloud-account/index.md). :::: + +## Managing multiple organizations + +You can create or access multiple organizations from a single {{ecloud}} account. + +You might want to create multiple organizations for reasons such as the following: + +* You want to separate management of your {{ecloud}} resources and settings for different use cases or teams. +* You want to create a [trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#trial-information) to evaluate additional {{ecloud}} features or solutions. + +Each organization has its own set of resources, users, settings, and billing and licensing. + +You need to be logged in to the organization you want to manage to make changes to its resources and settings. [Learn how to manage multiple organizations](/deploy-manage/deploy/elastic-cloud/manage-organizations.md). \ No newline at end of file diff --git a/deploy-manage/cloud-organization/billing.md b/deploy-manage/cloud-organization/billing.md index d9be1a34a8..81d72a5b0f 100644 --- a/deploy-manage/cloud-organization/billing.md +++ b/deploy-manage/cloud-organization/billing.md @@ -5,8 +5,8 @@ mapped_pages: - https://www.elastic.co/guide/en/serverless/current/general-billing-stop-project.html applies_to: deployment: - ess: all - serverless: all + ess: ga + serverless: ga products: - id: cloud-hosted - id: cloud-serverless diff --git a/deploy-manage/cloud-organization/billing/add-billing-details.md b/deploy-manage/cloud-organization/billing/add-billing-details.md index 97761fee02..904d8765d1 100644 --- a/deploy-manage/cloud-organization/billing/add-billing-details.md +++ b/deploy-manage/cloud-organization/billing/add-billing-details.md @@ -3,8 +3,8 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-billing-details.html applies_to: deployment: - ess: all - serverless: all + ess: ga + serverless: ga products: - id: cloud-hosted --- diff --git a/deploy-manage/cloud-organization/billing/billing-faq.md b/deploy-manage/cloud-organization/billing/billing-faq.md index 59345dbae7..6dd12fe762 100644 --- a/deploy-manage/cloud-organization/billing/billing-faq.md +++ b/deploy-manage/cloud-organization/billing/billing-faq.md @@ -3,11 +3,11 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-faq-billing.html applies_to: deployment: - self: - ece: - eck: - ess: all - serverless: all + self: ga + ece: ga + eck: ga + ess: ga + serverless: ga products: - id: cloud-hosted --- diff --git a/deploy-manage/cloud-organization/delete-organization.md b/deploy-manage/cloud-organization/delete-organization.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/deploy-manage/cloud-organization/manage-multiple-organizations.md b/deploy-manage/cloud-organization/manage-multiple-organizations.md new file mode 100644 index 0000000000..0bc5216c69 --- /dev/null +++ b/deploy-manage/cloud-organization/manage-multiple-organizations.md @@ -0,0 +1,90 @@ +--- +applies_to: + deployment: + ess: ga + serverless: ga +products: + - id: cloud-hosted + - id: cloud-serverless +--- + +# Manage multiple {{ecloud}} organizations + +You can create or access multiple organizations from a single {{ecloud}} account. + +You might want to create multiple organizations for reasons such as the following: + +* You want to separate management of your {{ecloud}} resources and settings for different use cases or teams. +* You want to create a [trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#trial-information) to evaluate additional {{ecloud}} features or solutions. + +Although you can access multiple organizations from the same {{ecloud}} account, each organization is independent. Each organization has its own set of resources, users, settings, and billing and licensing. Because of this, you need to be logged in to the organization you want to manage to make changes to its resources and settings. + +You can perform the following tasks to manage multiple organizations: + +* [Create a new organization](#create-a-new-organization) +* [View the organizations you have access to](#view-organizations) +* [Switch to a different organization](#switch-to-a-different-organization) +% * [Delete an organization](#delete-an-organization) + +## View the organizations you have access to + +You can view the organizations you have access to from the **Overview** page. + +To view the organizations: + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, click on the user menu and select **Profile**. +3. Click the **My organizations** tab. + +The organizations you have access to appear in the **My organizations** list. In the list, you can view the organization's name, its status, your roles in the organization, and when you were added to the organization. + +% confirm list name, confirm that "added" is when you were added to the organization + +:::{note} +Role information is refreshed only when you log in to the organization, and might be out of date if you haven't logged in recently. +::: + +:::{tip} +You can also access your organizations list by clicking the **My organizations** button on the **Organization** page. +::: + +## Create a new organization + +You can create a new organization at any time. Each organization starts with its own [14-day trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#trial-information). + +To create a new organization: + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, click on the user menu and select **Profile**. +3. Click the **My organizations** tab. +4. From the **Organizations** page, click {icon}`plus` **Create organization**. +5. Enter an optional name for your organization, and then click **Create organization**. + +After you create the organization, you can switch to it by clicking the organization name in the **Organizations** list. + +:::{tip} +You can also create a new organization by clicking on your current organization name and selecting {icon}`plus` **Create**. +::: + +## Switch to a different organization + +You can switch between organizations at any time. Depending on the authentication requirements for the organization, you might be required to re-authenticate. + +### From your user profile + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, click on the user menu and select **Profile**. +3. Click the **My organizations** tab. +4. Click the name of the organization you want to switch to. If it doesn't appear in the list, click **Manage organizations** to view all of the organizations you have access to. + +### From the My organizations menu + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, in the breadcrumb list, click the name of your current organization. +3. Click on the organization that you want to log into, or +4. Click the **My organizations** tab. +5. Click the name of the organization you want to switch to. + +% ## Delete an organization + +% Can it be done? \ No newline at end of file diff --git a/deploy-manage/cloud-organization/operational-emails.md b/deploy-manage/cloud-organization/operational-emails.md index c527298547..e457bc2c98 100644 --- a/deploy-manage/cloud-organization/operational-emails.md +++ b/deploy-manage/cloud-organization/operational-emails.md @@ -3,7 +3,7 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-operational-emails.html applies_to: deployment: - ess: all + ess: ga products: - id: cloud-hosted --- diff --git a/deploy-manage/cloud-organization/tools-and-apis.md b/deploy-manage/cloud-organization/tools-and-apis.md index 4dc897bdb5..70e7a9fd3a 100644 --- a/deploy-manage/cloud-organization/tools-and-apis.md +++ b/deploy-manage/cloud-organization/tools-and-apis.md @@ -4,6 +4,10 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-work-with-apis.html products: - id: cloud-hosted +applies_to: + deployment: + ech: ga + serverless: ga --- # Tools and APIs for your Cloud organization [ec-work-with-apis] diff --git a/deploy-manage/deploy/elastic-cloud/create-an-organization.md b/deploy-manage/deploy/elastic-cloud/create-an-organization.md index d82512cc4b..4bfda69fb7 100644 --- a/deploy-manage/deploy/elastic-cloud/create-an-organization.md +++ b/deploy-manage/deploy/elastic-cloud/create-an-organization.md @@ -13,27 +13,22 @@ products: - id: cloud-serverless --- -# Sign up and create an organization +# Sign up - -To sign up: +To get started with {{ecloud}}, sign up for an account: 1. Go to the [{{ecloud}} Sign Up](https://cloud.elastic.co/registration?page=docs&placement=docs-body) page. 2. Choose one of the available sign up methods. You can register with your email address and a password, use a Google or Microsoft account, or [subscribe from a Marketplace](../../../deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md). -:::{note} -* You can only belong to one {{ecloud}} organization at a time. If you want to create or join another organization, you must [leave the previous one](/cloud-account/join-or-leave-an-organization.md#ec-leave-organization) or use a different email address. -* An email address can’t be used for more than one {{ecloud}} account. To make the email address available for a new account, you can [remove it from your existing account](/cloud-account/update-your-email-address.md#sign-up-existing). -::: - When you first sign up, you create an organization and start with a trial license. -This organization is the umbrella for all of your {{ecloud}} resources, users, and account settings. Every organization has a unique identifier. Bills are invoiced according to the billing contact and details that you set for your organization. For more details on how to manage your organization, refer to [](/deploy-manage/cloud-organization.md). - +An organization is the umbrella for all of your {{ecloud}} resources, users, and account settings. Every organization has a unique identifier. Bills are invoiced according to the billing contact and details that you set for your organization. A user can belong to multiple organizations, or be the owner of multiple organizations. For more details on how to manage your organizations, refer to [](/deploy-manage/cloud-organization.md). ## Trial information [general-sign-up-trial-what-is-included-in-my-trial] -Your free 14-day trial includes: +When you create an organization, you start with a free 14-day trial. During this trial, you have access to the following: + +% do we want to tell them that they have unlimited trials by creating multiple organizations? **One hosted deployment** @@ -49,7 +44,7 @@ For more information, check the [{{ech}} documentation](cloud-hosted.md). * [Observability](../../../solutions/observability.md) * [Security](../../../solutions/security.md) -When you create a project, you select the project type applicable to your use case, so only the relevant and impactful applications and features are easily accessible to you. +When you create a project, you select the project type applicable to your use case, so the most relevant applications and features are surfaced for you from the start. For more information, check the [{{serverless-short}} documentation](serverless.md). @@ -82,7 +77,6 @@ When your trial expires, the deployment and projects that you created during the If you’re interested in learning more ways to subscribe to {{ecloud}}, don’t hesitate to [contact us](https://www.elastic.co/contact). - ## How do I get help? [ec_how_do_i_get_help] We’re here to help. If you have any questions feel free to reach out to [Support](https://cloud.elastic.co/support). diff --git a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md index cea7091a06..06633da308 100644 --- a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md @@ -11,6 +11,8 @@ products: # Subscribe from a marketplace [ec-marketplaces] +% updates todo + You can subscribe to {{ecloud}} from a marketplace. Your subscription gets billed together with other services that you’re already using, and can contribute towards your spend commitment with cloud providers. Trial availability and duration can vary depending on the marketplace. diff --git a/deploy-manage/users-roles.md b/deploy-manage/users-roles.md index 175011a2cf..04761bf2a5 100644 --- a/deploy-manage/users-roles.md +++ b/deploy-manage/users-roles.md @@ -3,8 +3,8 @@ navigation_title: Users and roles mapped_pages: - https://www.elastic.co/guide/en/serverless/current/project-settings-access.html applies_to: - stack: all - serverless: all + stack: ga + serverless: ga products: - id: cloud-serverless --- diff --git a/deploy-manage/users-roles/cloud-organization.md b/deploy-manage/users-roles/cloud-organization.md index 6d056df64a..b3972a6b0c 100644 --- a/deploy-manage/users-roles/cloud-organization.md +++ b/deploy-manage/users-roles/cloud-organization.md @@ -4,8 +4,8 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-organizations.html applies_to: deployment: - ess: all - serverless: all + ess: ga + serverless: ga products: - id: cloud-hosted --- @@ -29,7 +29,7 @@ If you're using {{ech}}, then you can also manage users and control access [at t ## Should I use organization-level or deployment-level SSO? [organization-deployment-sso] ```{applies_to} -ess: all +ess: ga ``` :::{include} _snippets/org-vs-deploy-sso.md diff --git a/deploy-manage/users-roles/cloud-organization/manage-users.md b/deploy-manage/users-roles/cloud-organization/manage-users.md index 3cb8d9f621..2b5b90b252 100644 --- a/deploy-manage/users-roles/cloud-organization/manage-users.md +++ b/deploy-manage/users-roles/cloud-organization/manage-users.md @@ -5,8 +5,8 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-api-organizations.html applies_to: deployment: - ess: all - serverless: all + ech: ga + serverless: ga products: - id: cloud-hosted - id: cloud-serverless @@ -20,9 +20,7 @@ You can invite users to join your organization to allow them to interact with al Alternatively, [configure {{ecloud}} SAML SSO](../../../deploy-manage/users-roles/cloud-organization/configure-saml-authentication.md) to enable your organization members to join the {{ecloud}} organization automatically. -::::{note} -Users can only belong to one organization at a time. If a user that you want to invite already belongs to a different organization, that user first needs to leave their current organization, or to use a different email address. Check [Join an organization from an existing {{ecloud}} account](/cloud-account/join-or-leave-an-organization.md). -:::: +An {{ecloud}} account can belong to multiple organizations. However, the user's roles and the resources that they have access to are controlled at the organization level. :::{tip} If you're using {{ech}}, then you can also manage users and control access [at the deployment level](/deploy-manage/users-roles/cluster-or-deployment-auth.md). @@ -40,7 +38,7 @@ To invite users to your organization: To add multiple members, enter the member email addresses, separated by a space. -5. If desired, assign roles to the users so that they automatically get the appropriate permissions when they accept the invitation and sign in to {{ecloud}}. +5. If desired, assign roles to the users so that they automatically get the appropriate permissions when they accept the invitation and sign in to your organization. If you're assigning roles for {{serverless-full}} projects, then you can grant access to all projects of the same type with a unique role, or select individual roles for specific projects. For more details about roles, refer to [](/deploy-manage/users-roles/cloud-organization/user-roles.md). @@ -99,6 +97,7 @@ curl -XGET \ -H "Authorization: ApiKey $EC_API_KEY" \ "https://api.elastic-cloud.com/api/v1/organizations/$ORGANIZATION_ID/invitations" ``` +::: :::{dropdown} View members in your organization From 651570919f0f37141bf18206a92c58e0781f7e15 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Tue, 3 Mar 2026 16:41:49 -0500 Subject: [PATCH 02/19] more --- cloud-account/index.md | 37 ++++++++----- .../join-or-leave-an-organization.md | 28 +++------- cloud-account/switch-organizations.md | 31 +++++++++++ cloud-account/toc.yml | 1 + cloud-account/update-your-email-address.md | 13 +++-- deploy-manage/cloud-organization.md | 8 +-- .../_snippets/switch-orgs.md | 18 +++++++ .../cloud-organization/_snippets/view-orgs.md | 21 ++++++++ .../cloud-organization/delete-organization.md | 0 .../manage-multiple-organizations.md | 52 ++++--------------- deploy-manage/toc.yml | 1 + .../cloud-organization/manage-users.md | 2 +- .../cloud-organization/user-roles.md | 4 +- 13 files changed, 127 insertions(+), 89 deletions(-) create mode 100644 deploy-manage/cloud-organization/_snippets/switch-orgs.md create mode 100644 deploy-manage/cloud-organization/_snippets/view-orgs.md delete mode 100644 deploy-manage/cloud-organization/delete-organization.md diff --git a/cloud-account/index.md b/cloud-account/index.md index 384d6728bd..157e68bdc8 100644 --- a/cloud-account/index.md +++ b/cloud-account/index.md @@ -16,24 +16,37 @@ description: Manage your Elastic Cloud account settings, including email, passwo # Manage your Cloud account and preferences +This section explains how to manage your {{ecloud}} account as a user, including your account settings, organizations, and interface preferences. + +::::{tip} +This section covers only your personal account. Organization-wide settings, such as user permissions and organization-level access controls, are managed by organization administrators. + +For information on organization and access management, refer to: +- [Manage your Cloud organization](/deploy-manage/cloud-organization.md) +- [Manage user roles and permissions](/deploy-manage/users-roles/cloud-organization/user-roles.md) +:::: + + +## Manage your account settings + Your {{ecloud}} account allows you to manage your personal settings, including your email address, password, and authentication methods. You can perform the following tasks at any time from your user profile: -* [Update your email address](/cloud-account/update-your-email-address.md) -* [Add an additional login method](/cloud-account/add-a-login-method.md): Choose from password-based login, Google sign-in, and Microsoft sign-in. +* [](/cloud-account/update-your-email-address.md) +* [](/cloud-account/add-a-login-method.md): Choose from password-based login, Google sign-in, and Microsoft sign-in. + If you use password-based login, then you can perform the following additional tasks: -* [Change your password](/cloud-account/change-your-password.md) -* [Configure multifactor authentication](/cloud-account/multifactor-authentication.md) +* [](/cloud-account/change-your-password.md) +* [](/cloud-account/multifactor-authentication.md) -Additionally, you can manage your organization membership, including joining or leaving an organization. Refer to [Join or leave an organization](/cloud-account/join-or-leave-an-organization.md) for more information. +## Manage your organizations -Some options also let you set personal preferences and customize the interface, such as [using dark mode](dark-mode.md) in your projects and deployments. +Organizations are groupings of {{ecloud}} resources and associated settings. As an {{ecloud}} user, you can be a member of multiple organizations. -::::{tip} -This section focuses on the actions you can take as an individual user to manage your own account. It does not cover organization-wide settings, such as managing user permissions or configuring organization-level access controls, which are handled by the organization administrators. +* [](/cloud-account/join-or-leave-an-organization.md) +* [View and switch between organizations](/cloud-account/switch-organizations.md) -For information on organization and access management, refer to: -- [Manage your Cloud organization](/deploy-manage/cloud-organization.md) -- [Manage user roles and permissions](/deploy-manage/users-roles/cloud-organization/user-roles.md) -:::: +## Customize your interface + +Some options also let you set personal preferences and customize the interface, such as [using dark mode](dark-mode.md) in your projects and deployments. \ No newline at end of file diff --git a/cloud-account/join-or-leave-an-organization.md b/cloud-account/join-or-leave-an-organization.md index 700a387e7a..f5b9fe1896 100644 --- a/cloud-account/join-or-leave-an-organization.md +++ b/cloud-account/join-or-leave-an-organization.md @@ -11,38 +11,22 @@ products: - id: cloud-serverless --- -% EDIT ME! - # Join or leave an organization -Organizations in {{ecloud}} group user accounts, projects and deployments under a common billing and access structure. If you have been invited to an organization, you can accept the invitation and become a member. You can also leave an organization at any time, as long as you don’t have active projects or deployments associated with your account. +Organizations in {{ecloud}} group user accounts, projects and deployments under a common billing and access structure. If you have been invited to an organization, you can accept the invitation and become a member. You can join multiple organizations, or [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). + +You can also leave an organization at any time, as long as you don’t have active projects or deployments associated with your account. -This guide explains how to join or leave an organization, including steps for handling projects and deployments when switching organizations. +This guide explains how to join or leave an organization. To learn how to view organizations you have access to and switch between them, refer to [](switch-organizations.md). ## Accept an invitation [ec-accept-invitation] Invitations to join an organization are sent by email. Invited users have 72 hours to accept the invitation. If they do not join within that period, an administrator of the organization will have to send a new invitation. Refer to [manage users](/deploy-manage/users-roles/cloud-organization/manage-users.md) for more information. +If you're a member of more than one organization, then after you accept an invitation, the new organization appears in your list of organizations. You can switch to the new organization by clicking the organization name in the list. Refer to [Switch between organizations](/cloud-account/switch-organizations.md) for more information. + ## Leave an organization [ec-leave-organization] On the **Members** tab of the **Organization** page, click the three dots corresponding to your email address and select **Leave organization**. If you’re the only user in the organization, you can only leave if you deleted all your deployments and projects, and you don’t have pending bills. - -## Join an organization from an existing {{ecloud}} account [ec-join-invitation] - -If you already belong to an organization, and you want to join a new one you will need to leave your existing organization and follow this steps: - -1. Make sure you do not have active projects or deployments before you leave your current organization. -2. Delete your projects or deployments and clear any bills. -3. Leave your current organization. -4. Ask the administrator to invite you to the organization you want to join. -5. Accept the invitation that you will get by email. - -Alternatively, for Elastic Cloud Hosted deployments, there's a possibility to migrate your deployments to the new organization through back up and restore operations. In such case: - -1. [Back up your deployments to any private repository](/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md) so that you can restore them to your new organization. -2. Leave your current organization. -3. Ask the administrator to invite you to the organization you want to join. -4. Accept the invitation that you will get by email. -5. Configure the private repository in your new organization and restore the backup you took in step 1. diff --git a/cloud-account/switch-organizations.md b/cloud-account/switch-organizations.md index e69de29bb2..a092054d64 100644 --- a/cloud-account/switch-organizations.md +++ b/cloud-account/switch-organizations.md @@ -0,0 +1,31 @@ +--- +applies_to: + deployment: + ess: ga + serverless: ga +products: + - id: cloud-hosted +--- + +# Switch between organizations + +From a single {{ecloud}} account, you can access multiple organizations. + +You might be a member of multiple organizations in cases such as the following: + +* You use different organizations for different use cases or teams. +* You're a consultant working with multiple clients who have different {{ecloud}} organizations. + +You can switch between organizations at any time. Depending on the organization that you're switching to, you might be required to re-authenticate. + +If you're an organization owner, then you can learn more about managing multiple organizations in [](/deploy-manage/cloud-organization/manage-multiple-organizations.md). + +:::{tip} +To join an additional organization, [accept an invitation](/cloud-account/join-or-leave-an-organization.md#ec-accept-invitation) to join the organization. You can also [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). +::: + +:::{include} /deploy-manage/cloud-organization/_snippets/view-orgs.md +::: + +:::{include} /deploy-manage/cloud-organization/_snippets/switch-orgs.md +::: \ No newline at end of file diff --git a/cloud-account/toc.yml b/cloud-account/toc.yml index 967d4fcad8..7d11449dfb 100644 --- a/cloud-account/toc.yml +++ b/cloud-account/toc.yml @@ -6,5 +6,6 @@ toc: - file: change-your-password.md - file: add-a-login-method.md - file: multifactor-authentication.md + - file: switch-organizations.md - file: dark-mode.md - file: high-contrast.md \ No newline at end of file diff --git a/cloud-account/update-your-email-address.md b/cloud-account/update-your-email-address.md index b8777883ed..8d6769a060 100644 --- a/cloud-account/update-your-email-address.md +++ b/cloud-account/update-your-email-address.md @@ -13,7 +13,7 @@ products: Each {{ecloud}} account has a primary email associated with it. By default, the primary email address is used to sign up for {{ecloud}} and to log in. If needed, you can change this primary email address. -Your email address is used to uniquely identify you. It can’t be used for more than one {{ecloud}} account, whether that account is a trial account, a standard {{ecloud}} account, or a subscription account through a marketplace. An {{ecloud}} account can belong to only one organization at a time. +Your email address is used to uniquely identify you. It can’t be used for more than one {{ecloud}} account, whether that account is a trial account, a standard {{ecloud}} account, or a subscription account through a marketplace. However, a single {{ecloud}} account can belong to [multiple organizations](/cloud-account/switch-organizations.md). ## Change your email address (native sign-in) @@ -39,12 +39,15 @@ If your organization is associated with [Azure Marketplace](../deploy-manage/dep ## Sign up using an existing email address [sign-up-existing] +% is this still needed at all? + In some situations, you might want to create a new {{ecloud}} account using an email address that is already associated with an existing account. To sign up to {{ecloud}} using an email address associated with another {{ecloud}} account, you must remove the email address from your previous account and replace it with a new address. +:::{note} +You don't need to follow this procedure if you want to [join an additional organization](/cloud-account/join-or-leave-an-organization.md) or [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). One account can belong to and own multiple organizations. +::: + 1. Use your current email address (for example, `my.preferred.address@foobar.com`) to log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. Follow the steps from one of the procedures on this page to update that email address to another email address, such as `my.alternate.address@gmail.com`. -You can now use the email address from step 1 to do the following: - -* [Sign up for a new account](/deploy-manage/deploy/elastic-cloud/create-an-organization.md). -* [Join an existing organization](/cloud-account/join-or-leave-an-organization.md). \ No newline at end of file +You can now use the email address from step 1 to [sign up for a new account](/deploy-manage/deploy/elastic-cloud/create-an-organization.md). \ No newline at end of file diff --git a/deploy-manage/cloud-organization.md b/deploy-manage/cloud-organization.md index 3f22678673..a22e6420b3 100644 --- a/deploy-manage/cloud-organization.md +++ b/deploy-manage/cloud-organization.md @@ -15,7 +15,7 @@ An organization is the umbrella for a group of {{ecloud}} resources, users, and When you [sign up for {{ecloud}}](/deploy-manage/deploy/elastic-cloud/create-an-organization.md), you have the option to create a new organization. You also can be [added to an existing organization](/deploy-manage/users-roles/cloud-organization/manage-users.md). -The administrator of an organization is referred to as the organization owner, and belongs to the [Organization owner role](/deploy-manage/users-roles/cloud-organization/user-roles.md#organization-level-roles). An organization can have more than one organization owner. +The administrator of an organization is referred to as the organization owner, and belongs to the [Organization owner role](/deploy-manage/users-roles/cloud-organization/user-roles.md#ec_organization_level_roles). An organization can have more than one organization owner. ## Organization management tasks @@ -30,7 +30,7 @@ As an organization owner, you can perform the following tasks to manage your Clo * [Manage API keys](/deploy-manage/api-keys.md) to use with the [{{ecloud}}](https://www.elastic.co/docs/api/doc/cloud), [{{ecloud}} Billing](https://www.elastic.co/docs/api/doc/cloud-billing/), and [{{serverless-full}}](https://www.elastic.co/docs/api/doc/elastic-cloud-serverless) APIs * Configure who receives [operational emails](/deploy-manage/cloud-organization/operational-emails.md) related to your organization * Track the [status of {{ecloud}} services](/deploy-manage/cloud-organization/service-status.md) -* [Delete](/deploy-manage/cloud-organization/delete-an-organization.md) an organization. +% * [Delete](/deploy-manage/cloud-organization/delete-an-organization.md) an organization. Several aspects of your organization can also be managed using tools provided by Elastic. For a list of tools, refer to [{{ecloud}} organization tools and APIs](/deploy-manage/cloud-organization/tools-and-apis.md). @@ -45,8 +45,8 @@ You can create or access multiple organizations from a single {{ecloud}} account You might want to create multiple organizations for reasons such as the following: * You want to separate management of your {{ecloud}} resources and settings for different use cases or teams. -* You want to create a [trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#trial-information) to evaluate additional {{ecloud}} features or solutions. +* You want to create a [trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#general-sign-up-trial-what-is-included-in-my-trial) to evaluate additional {{ecloud}} features or solutions. Each organization has its own set of resources, users, settings, and billing and licensing. -You need to be logged in to the organization you want to manage to make changes to its resources and settings. [Learn how to manage multiple organizations](/deploy-manage/deploy/elastic-cloud/manage-organizations.md). \ No newline at end of file +You need to be logged in to the organization you want to manage to make changes to its resources and settings. [Learn how to manage multiple organizations](/deploy-manage/cloud-organization/manage-multiple-organizations.md). \ No newline at end of file diff --git a/deploy-manage/cloud-organization/_snippets/switch-orgs.md b/deploy-manage/cloud-organization/_snippets/switch-orgs.md new file mode 100644 index 0000000000..631f7bc08d --- /dev/null +++ b/deploy-manage/cloud-organization/_snippets/switch-orgs.md @@ -0,0 +1,18 @@ +## Switch to a different organization + +You can switch between organizations at any time. Depending on the authentication requirements for the organization, you might be required to re-authenticate. + +### From your user profile + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, click on the user menu and select **Profile**. +3. Click the **My organizations** tab. +4. Click the name of the organization you want to switch to. If it doesn't appear in the list, click **Manage organizations** to view all of the organizations you have access to. + +### From the My organizations menu + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, in the breadcrumb list, click the name of your current organization. +3. Click on the organization that you want to log into, or +4. Click the **My organizations** tab. +5. Click the name of the organization you want to switch to. \ No newline at end of file diff --git a/deploy-manage/cloud-organization/_snippets/view-orgs.md b/deploy-manage/cloud-organization/_snippets/view-orgs.md new file mode 100644 index 0000000000..a90ab7bfe6 --- /dev/null +++ b/deploy-manage/cloud-organization/_snippets/view-orgs.md @@ -0,0 +1,21 @@ +## View the organizations you have access to [view-organizations] + +You can view the organizations you have access to from the **Overview** page. + +To view the organizations: + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, click on the user menu and select **Profile**. +3. Click the **My organizations** tab. + +The organizations you have access to appear in the **My organizations** list. In the list, you can view the organization's name, its status, your roles in the organization, and when you were added to the organization. + +% confirm list name, confirm that "added" is when you were added to the organization + +:::{note} +Role information is refreshed only when you log in to the organization, and might be out of date if you haven't logged in recently. +::: + +:::{tip} +You can also access your organizations list by clicking the **My organizations** button on the **Organization** page. +::: \ No newline at end of file diff --git a/deploy-manage/cloud-organization/delete-organization.md b/deploy-manage/cloud-organization/delete-organization.md deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/deploy-manage/cloud-organization/manage-multiple-organizations.md b/deploy-manage/cloud-organization/manage-multiple-organizations.md index 0bc5216c69..fe701b0460 100644 --- a/deploy-manage/cloud-organization/manage-multiple-organizations.md +++ b/deploy-manage/cloud-organization/manage-multiple-organizations.md @@ -6,6 +6,7 @@ applies_to: products: - id: cloud-hosted - id: cloud-serverless +navigation_title: Manage multiple organizations --- # Manage multiple {{ecloud}} organizations @@ -15,7 +16,7 @@ You can create or access multiple organizations from a single {{ecloud}} account You might want to create multiple organizations for reasons such as the following: * You want to separate management of your {{ecloud}} resources and settings for different use cases or teams. -* You want to create a [trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#trial-information) to evaluate additional {{ecloud}} features or solutions. +* You want to create a [trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#general-sign-up-trial-what-is-included-in-my-trial) to evaluate additional {{ecloud}} features or solutions. Although you can access multiple organizations from the same {{ecloud}} account, each organization is independent. Each organization has its own set of resources, users, settings, and billing and licensing. Because of this, you need to be logged in to the organization you want to manage to make changes to its resources and settings. @@ -26,65 +27,30 @@ You can perform the following tasks to manage multiple organizations: * [Switch to a different organization](#switch-to-a-different-organization) % * [Delete an organization](#delete-an-organization) -## View the organizations you have access to - -You can view the organizations you have access to from the **Overview** page. - -To view the organizations: - -1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. From the top navigation menu, click on the user menu and select **Profile**. -3. Click the **My organizations** tab. - -The organizations you have access to appear in the **My organizations** list. In the list, you can view the organization's name, its status, your roles in the organization, and when you were added to the organization. - -% confirm list name, confirm that "added" is when you were added to the organization - -:::{note} -Role information is refreshed only when you log in to the organization, and might be out of date if you haven't logged in recently. -::: - -:::{tip} -You can also access your organizations list by clicking the **My organizations** button on the **Organization** page. +:::{include} _snippets/view-orgs.md ::: ## Create a new organization -You can create a new organization at any time. Each organization starts with its own [14-day trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#trial-information). +You can create a new organization at any time. Each organization starts with its own [14-day trial](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#general-sign-up-trial-what-is-included-in-my-trial). To create a new organization: 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. From the top navigation menu, click on the user menu and select **Profile**. 3. Click the **My organizations** tab. -4. From the **Organizations** page, click {icon}`plus` **Create organization**. +4. From the **Organizations** page, click {icon}`plus_in_circle` **Create organization**. 5. Enter an optional name for your organization, and then click **Create organization**. After you create the organization, you can switch to it by clicking the organization name in the **Organizations** list. :::{tip} -You can also create a new organization by clicking on your current organization name and selecting {icon}`plus` **Create**. +You can also create a new organization by clicking on your current organization name and selecting {icon}`plus_in_circle` **Create**. ::: -## Switch to a different organization - -You can switch between organizations at any time. Depending on the authentication requirements for the organization, you might be required to re-authenticate. - -### From your user profile - -1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. From the top navigation menu, click on the user menu and select **Profile**. -3. Click the **My organizations** tab. -4. Click the name of the organization you want to switch to. If it doesn't appear in the list, click **Manage organizations** to view all of the organizations you have access to. - -### From the My organizations menu - -1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. From the top navigation menu, in the breadcrumb list, click the name of your current organization. -3. Click on the organization that you want to log into, or -4. Click the **My organizations** tab. -5. Click the name of the organization you want to switch to. +:::{include} _snippets/switch-orgs.md +::: % ## Delete an organization -% Can it be done? \ No newline at end of file +% Can it be done? Do we want to document this? \ No newline at end of file diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 56c21e4eb1..5e72c0815b 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -781,6 +781,7 @@ toc: - file: kibana-reporting-configuration.md - file: cloud-organization.md children: + - file: cloud-organization/manage-multiple-organizations.md - file: cloud-organization/billing.md children: - file: cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md diff --git a/deploy-manage/users-roles/cloud-organization/manage-users.md b/deploy-manage/users-roles/cloud-organization/manage-users.md index 2b5b90b252..0d063f7545 100644 --- a/deploy-manage/users-roles/cloud-organization/manage-users.md +++ b/deploy-manage/users-roles/cloud-organization/manage-users.md @@ -48,7 +48,7 @@ To invite users to your organization: ## Manage existing users -On the **Members** tab of the **Organization** page, you can view the list of current members, including status and role. +On the **Members** tab of the **Organization** page, you can view the list of current members, including their status, role, and any other organizations that they are members of. In the **Actions** column, click the three dots to edit a member’s role, or revoke an invite, or remove a member from your organization. diff --git a/deploy-manage/users-roles/cloud-organization/user-roles.md b/deploy-manage/users-roles/cloud-organization/user-roles.md index 3eeb8defbb..6d9d9c45bb 100644 --- a/deploy-manage/users-roles/cloud-organization/user-roles.md +++ b/deploy-manage/users-roles/cloud-organization/user-roles.md @@ -4,8 +4,8 @@ mapped_pages: - https://www.elastic.co/guide/en/serverless/current/general-manage-organization.html applies_to: deployment: - ess: all - serverless: all + ess: ga + serverless: ga products: - id: cloud-hosted - id: cloud-serverless From fb9af29ffaed8cf3bdb5f49deab4f6003d84997b Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Tue, 3 Mar 2026 16:44:53 -0500 Subject: [PATCH 03/19] remove all of your" --- deploy-manage/deploy/elastic-cloud/create-an-organization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/create-an-organization.md b/deploy-manage/deploy/elastic-cloud/create-an-organization.md index 4bfda69fb7..3cedbeafa9 100644 --- a/deploy-manage/deploy/elastic-cloud/create-an-organization.md +++ b/deploy-manage/deploy/elastic-cloud/create-an-organization.md @@ -22,7 +22,7 @@ To get started with {{ecloud}}, sign up for an account: When you first sign up, you create an organization and start with a trial license. -An organization is the umbrella for all of your {{ecloud}} resources, users, and account settings. Every organization has a unique identifier. Bills are invoiced according to the billing contact and details that you set for your organization. A user can belong to multiple organizations, or be the owner of multiple organizations. For more details on how to manage your organizations, refer to [](/deploy-manage/cloud-organization.md). +An organization is the umbrella for a group of {{ecloud}} resources, users, and account settings. Every organization has a unique identifier. Bills are invoiced according to the billing contact and details that you set for your organization. A user can belong to multiple organizations, or be the owner of multiple organizations. For more details on how to manage your organizations, refer to [](/deploy-manage/cloud-organization.md). ## Trial information [general-sign-up-trial-what-is-included-in-my-trial] From a5977586e13a61e52ac259f5e26fd2b462a04ded Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 26 Mar 2026 16:14:46 -0400 Subject: [PATCH 04/19] coverage --- .../manage-multiple-organizations.md | 12 +++++++++--- .../_snippets/invite-additional-orgs.md | 7 +++++++ .../_snippets/view-org-memberships.md | 9 +++++++++ .../users-roles/cloud-organization/manage-users.md | 10 ++++++++++ 4 files changed, 35 insertions(+), 3 deletions(-) create mode 100644 deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md create mode 100644 deploy-manage/users-roles/cloud-organization/_snippets/view-org-memberships.md diff --git a/deploy-manage/cloud-organization/manage-multiple-organizations.md b/deploy-manage/cloud-organization/manage-multiple-organizations.md index fe701b0460..1f9c0f5e15 100644 --- a/deploy-manage/cloud-organization/manage-multiple-organizations.md +++ b/deploy-manage/cloud-organization/manage-multiple-organizations.md @@ -25,7 +25,7 @@ You can perform the following tasks to manage multiple organizations: * [Create a new organization](#create-a-new-organization) * [View the organizations you have access to](#view-organizations) * [Switch to a different organization](#switch-to-a-different-organization) -% * [Delete an organization](#delete-an-organization) +* [Invite users to join additional organizations](#invite-users-to-join-additional-organizations) :::{include} _snippets/view-orgs.md ::: @@ -51,6 +51,12 @@ You can also create a new organization by clicking on your current organization :::{include} _snippets/switch-orgs.md ::: -% ## Delete an organization +## Invite users to join additional organizations [invite-additional-orgs] -% Can it be done? Do we want to document this? \ No newline at end of file +:::{include} _snippets/invite-additional-orgs.md +::: + +## View your users' organization memberships + +:::{include} _snippets/view-users-org-memberships.md +::: \ No newline at end of file diff --git a/deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md b/deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md new file mode 100644 index 0000000000..0e97b531a1 --- /dev/null +++ b/deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md @@ -0,0 +1,7 @@ +Because users are managed at the organization level, you must [invite users](/deploy-manage/users-roles/cloud-organization/manage-users.md#ec-invite-users) from within the organization that you want them to join. You can't invite users to join multiple organizations at once. + +If a user already has an {{ecloud}} account, then they don't need to sign up again. Instead, they can log in with their selected login method. + +If your organization uses [SAML SSO](/deploy-manage/users-roles/cloud-organization/configure-saml-authentication.md), then you don't need to invite users to join the organization. Users are added to the organization automatically when they log in to your identity provider SSO URL. + +Organizations can have different authentication requirements. For example, one organization might enforce SAML SSO, while another organization might not enforce any specific login method. If your organization enforces a specific login method, then the user will need to use that method to log in, and might be prompted to re-authenticate. \ No newline at end of file diff --git a/deploy-manage/users-roles/cloud-organization/_snippets/view-org-memberships.md b/deploy-manage/users-roles/cloud-organization/_snippets/view-org-memberships.md new file mode 100644 index 0000000000..00bf379e7f --- /dev/null +++ b/deploy-manage/users-roles/cloud-organization/_snippets/view-org-memberships.md @@ -0,0 +1,9 @@ +You can view the organizations that your users are members of from the **Members** tab of the **Organization** page. This page shows which organizations each member of your current organization belongs to. + +To view the organizations: + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From a deployment or project on the home page, select **Manage**. +3. From the lower navigation menu, select **Organization**. +4. Click the **Members** tab. +5. Click the name of the user you want to view the organizations for. \ No newline at end of file diff --git a/deploy-manage/users-roles/cloud-organization/manage-users.md b/deploy-manage/users-roles/cloud-organization/manage-users.md index 0d063f7545..42ee22d4d0 100644 --- a/deploy-manage/users-roles/cloud-organization/manage-users.md +++ b/deploy-manage/users-roles/cloud-organization/manage-users.md @@ -46,12 +46,22 @@ To invite users to your organization: Invitations to join an organization are sent by email. Invited users have 72 hours to accept the invitation before it expires. If the invite has expired, an admin can resend the invitation. +## Invite users to join additional organizations [invite-additional-orgs] + +:::{include} _snippets/invite-additional-orgs.md +::: + ## Manage existing users On the **Members** tab of the **Organization** page, you can view the list of current members, including their status, role, and any other organizations that they are members of. In the **Actions** column, click the three dots to edit a member’s role, or revoke an invite, or remove a member from your organization. +## View your users' organization memberships + +:::{include} _snippets/view-org-memberships.md +::: + ## Manage users through the {{ecloud}} API [ec-api-organizations] You can also manage members of your organization using the [{{ecloud}} API](https://www.elastic.co/docs/api/doc/cloud/). From 3c9e7eb3012e0f05803ca0ef31e7704182025c33 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 26 Mar 2026 16:27:14 -0400 Subject: [PATCH 05/19] more --- .../cloud-organization/manage-multiple-organizations.md | 5 +++++ .../cloud-organization/_snippets/reconcile-email.md | 5 +++++ deploy-manage/users-roles/cloud-organization/manage-users.md | 5 +++++ 3 files changed, 15 insertions(+) create mode 100644 deploy-manage/users-roles/cloud-organization/_snippets/reconcile-email.md diff --git a/deploy-manage/cloud-organization/manage-multiple-organizations.md b/deploy-manage/cloud-organization/manage-multiple-organizations.md index 1f9c0f5e15..38bf1fc11d 100644 --- a/deploy-manage/cloud-organization/manage-multiple-organizations.md +++ b/deploy-manage/cloud-organization/manage-multiple-organizations.md @@ -56,6 +56,11 @@ You can also create a new organization by clicking on your current organization :::{include} _snippets/invite-additional-orgs.md ::: +## Reconcile alternative email addresses + +:::{include} /deploy-manage/users-roles/cloud-organization/_snippets/reconcile-email.md +::: + ## View your users' organization memberships :::{include} _snippets/view-users-org-memberships.md diff --git a/deploy-manage/users-roles/cloud-organization/_snippets/reconcile-email.md b/deploy-manage/users-roles/cloud-organization/_snippets/reconcile-email.md new file mode 100644 index 0000000000..81d0e904b9 --- /dev/null +++ b/deploy-manage/users-roles/cloud-organization/_snippets/reconcile-email.md @@ -0,0 +1,5 @@ +Before April 2026, each organization required its own {{ecloud}} account and email address. You can now use one {{ecloud}} account across multiple organizations, and you might want to remove redundant accounts. + +For each organization where a user currently signs in with a different email address, invite them again using the email address that you want them to use everywhere. Assign the same [roles and privileges](/deploy-manage/users-roles/cloud-organization/user-roles.md) they had on the alternate account. + +After the user accepts the invitation, you can [delete](/deploy-manage/users-roles/cloud-organization/manage-users.md#manage-existing-users) their alternate account from that organization. \ No newline at end of file diff --git a/deploy-manage/users-roles/cloud-organization/manage-users.md b/deploy-manage/users-roles/cloud-organization/manage-users.md index 42ee22d4d0..fc7489ff0f 100644 --- a/deploy-manage/users-roles/cloud-organization/manage-users.md +++ b/deploy-manage/users-roles/cloud-organization/manage-users.md @@ -57,6 +57,11 @@ On the **Members** tab of the **Organization** page, you can view the list of cu In the **Actions** column, click the three dots to edit a member’s role, or revoke an invite, or remove a member from your organization. +### Reconcile alternative email addresses + +:::{include} /deploy-manage/users-roles/cloud-organization/_snippets/reconcile-email.md +::: + ## View your users' organization memberships :::{include} _snippets/view-org-memberships.md From 60b780dad7b7d7fff927b193489a45176f618853 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Mon, 6 Apr 2026 13:25:43 -0400 Subject: [PATCH 06/19] Update deploy-manage/cloud-organization.md --- deploy-manage/cloud-organization.md | 1 - 1 file changed, 1 deletion(-) diff --git a/deploy-manage/cloud-organization.md b/deploy-manage/cloud-organization.md index 2762473c02..f88c204014 100644 --- a/deploy-manage/cloud-organization.md +++ b/deploy-manage/cloud-organization.md @@ -30,7 +30,6 @@ As an organization owner, you can perform the following tasks to manage your Clo * [Manage API keys](/deploy-manage/api-keys.md) to use with the [{{ecloud}}](https://www.elastic.co/docs/api/doc/cloud), [{{ecloud}} Billing](https://www.elastic.co/docs/api/doc/cloud-billing/), and [{{serverless-full}}](https://www.elastic.co/docs/api/doc/elastic-cloud-serverless) APIs. For {{serverless-full}} projects, you can also create {{ecloud}} API keys that grant access to project-level {{es}} and {{kib}} APIs. * Configure who receives [operational emails](/deploy-manage/cloud-organization/operational-emails.md) related to your organization * Track the [status of {{ecloud}} services](/deploy-manage/cloud-organization/service-status.md) -% * [Delete](/deploy-manage/cloud-organization/delete-an-organization.md) an organization. Several aspects of your organization can also be managed using tools provided by Elastic. For a list of tools, refer to [{{ecloud}} organization tools and APIs](/deploy-manage/cloud-organization/tools-and-apis.md). From 6363ba0006ec97c426996a7e3276a228342b34f7 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Mon, 6 Apr 2026 13:28:32 -0400 Subject: [PATCH 07/19] Apply suggestions from code review --- cloud-account/switch-organizations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/cloud-account/switch-organizations.md b/cloud-account/switch-organizations.md index a092054d64..081bd55a63 100644 --- a/cloud-account/switch-organizations.md +++ b/cloud-account/switch-organizations.md @@ -5,9 +5,10 @@ applies_to: serverless: ga products: - id: cloud-hosted +navigation_title: Switch between organizations --- -# Switch between organizations +# Switch between {{ecloud}} organizations From a single {{ecloud}} account, you can access multiple organizations. From f0ec3b1865977d27b60cecda73bbe36fa31ecb78 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Mon, 6 Apr 2026 13:53:03 -0400 Subject: [PATCH 08/19] fix build --- .../cloud-organization/manage-multiple-organizations.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/deploy-manage/cloud-organization/manage-multiple-organizations.md b/deploy-manage/cloud-organization/manage-multiple-organizations.md index 38bf1fc11d..d818c57456 100644 --- a/deploy-manage/cloud-organization/manage-multiple-organizations.md +++ b/deploy-manage/cloud-organization/manage-multiple-organizations.md @@ -25,7 +25,7 @@ You can perform the following tasks to manage multiple organizations: * [Create a new organization](#create-a-new-organization) * [View the organizations you have access to](#view-organizations) * [Switch to a different organization](#switch-to-a-different-organization) -* [Invite users to join additional organizations](#invite-users-to-join-additional-organizations) +* [Invite users to join additional organizations](#invite-additional-orgs) :::{include} _snippets/view-orgs.md ::: @@ -53,7 +53,7 @@ You can also create a new organization by clicking on your current organization ## Invite users to join additional organizations [invite-additional-orgs] -:::{include} _snippets/invite-additional-orgs.md +:::{include} /deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md ::: ## Reconcile alternative email addresses @@ -63,5 +63,5 @@ You can also create a new organization by clicking on your current organization ## View your users' organization memberships -:::{include} _snippets/view-users-org-memberships.md +:::{include} /deploy-manage/users-roles/cloud-organization/_snippets/view-org-memberships.md ::: \ No newline at end of file From 84b4232c14f56fc09563fe65e3441befc01c8f8c Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Tue, 7 Apr 2026 15:54:50 -0400 Subject: [PATCH 09/19] clean up azure isv docs --- .../azure-native-isv-service-logs-metrics.md | 130 ++++ ...zure-native-isv-service-troubleshooting.md | 104 ++++ .../elastic-cloud/azure-native-isv-service.md | 587 +++++------------- deploy-manage/toc.yml | 3 + redirects.yml | 22 +- 5 files changed, 420 insertions(+), 426 deletions(-) create mode 100644 deploy-manage/deploy/elastic-cloud/azure-native-isv-service-logs-metrics.md create mode 100644 deploy-manage/deploy/elastic-cloud/azure-native-isv-service-troubleshooting.md diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service-logs-metrics.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service-logs-metrics.md new file mode 100644 index 0000000000..7017ce22cb --- /dev/null +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service-logs-metrics.md @@ -0,0 +1,130 @@ +--- +applies_to: + deployment: + ess: ga + serverless: ga +products: + - id: cloud-hosted + - id: cloud-serverless +navigation_title: Logs and metrics +--- + +# Azure Native ISV Service logs and metrics + +$$$ec-azure-logs-and-metrics$$$ +$$$azure-integration-monitor$$$ + +The {{ecloud}} Azure Native ISV Service simplifies logging for Azure services with the {{stack}}. This integration supports: + +* Azure subscription logs +* Azure resources logs (check [Supported categories for Azure Resource Logs](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-categories?WT.mc_id=Portal-Azure_Marketplace_Elastic) for examples) + +::::{note} +If you want to send platform logs to a deployment that has [network security policies](/deploy-manage/security/network-security.md) applied, then you need to contact [the Elastic Support Team](azure-native-isv-service-troubleshooting.md#azure-integration-support) to perform additional configurations. Refer support to the article [Azure++ Resource Logs blocked by Traffic Filters](https://support.elastic.co/knowledge/18603788). +:::: + + +## Unsupported log types + +The following log types are not supported as part of this integration: + +* Azure tenant logs +* Logs from Azure compute services, such as Virtual Machines + + +## Configure log ingestion + +::::{note} +If your Azure resources and Elastic deployment or project are in different subscriptions, before creating diagnostic settings confirm that the `Microsoft.Elastic` resource provider is registered in the subscription in which the Azure resources exist. If not, register the resource provider following these steps: + +1. In Azure, navigate to **Subscriptions → Resource providers**. +2. Search for `Microsoft.Elastic` and check that it is registered. + +If you already created diagnostic settings before the `Microsoft.Elastic` resource provider was registered, delete and add the diagnostic setting again. +:::: + +In the Azure console, configure the ingestion of Azure logs into either a new or existing {{ecloud}} deployment or project: + +* When creating a new deployment or project, use the **Logs & metrics** tab in Azure to specify the log type and a key/value tag pair. Any Azure resources that match on the tag value automatically send log data to the {{ecloud}} deployment or project, once it's been created. + +:::{image} /deploy-manage/images/cloud-ec-marketplace-azure004.png +:alt: The Logs & Metrics tab on the Create Elastic Resource page +::: + +* For existing deployments or projects, configure Azure logs from the [resource overview page](https://portal.azure.com/#browse/Microsoft.Elastic%2Fmonitors) in the Azure console. + +::::{important} +Note the following restrictions for logging: + +* Only logs from non-compute Azure services are ingested as part of the configuration detailed in this document. Logs from compute services, such as Virtual Machines, into the {{stack}} will be added in a future release. + +* The Azure services must be in one of the [supported regions](cloud://reference/cloud-hosted/ec-regions-templates-instances.md#ec-azure_regions). All regions will be supported in the future. +:::: + +::::{note} +Your Azure logs might sometimes contain references to a user `Liftr_Elastic`. This user is created automatically by Azure as part of the integration with {{ecloud}}. +:::: + + +## Monitor ingestion status + +To check which of your Azure resources are currently being monitored, navigate to your {{es}} deployment or project and open the **Monitored resources** tab. Each resource shows one of the following status indicators: + +| Status | Description | +| --- | --- | +| **Sending** | Logs are currently being sent to the {{es}} cluster. | +| **Logs not configured** | Log collection is currently not configured for the resource. Open the **Edit tags** link to configure which logs are collected. For details about tagging resources, check [Use tags to organize your Azure resources and management hierarchy](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources?tabs=json) in the Azure documentation. | +| **N/A** | Monitoring is not available for this resource type. | +| **Limit reached** | Azure resources can send diagnostic data to a maximum of five outputs. Data is not being sent to the {{es}} cluster because the output limit has already been reached. | +| **Failed** | Logs are configured but failed to ship to the {{es}} cluster. For help resolving this problem you can [contact Support](azure-native-isv-service-troubleshooting.md#azure-integration-support). | +| **Region not supported** | The Azure resource must be in one of the [supported regions](cloud://reference/cloud-hosted/ec-regions-templates-instances.md#ec-azure_regions). | + + +$$$azure-integration-ingest-metrics$$$ + +## Ingest metrics + +Metrics are not supported as part of the current {{ecloud}} Azure Native ISV Service. This will be implemented in a future phase. Metrics can still be collected from all Azure services using {{metricbeat}}. For details, check [Ingest other Azure metrics using the {{metricbeat}} Azure module](../../../solutions/observability/cloud/monitor-microsoft-azure-with-beats.md#azure-step-four). + + +$$$azure-integration-vm-extensions$$$ + +## Monitor virtual machines + +You can monitor your Azure virtual machines by installing the {{agent}} VM extension. Once enabled, the VM extension downloads the {{agent}}, installs it, and enrols it to {{fleet-server}}. The {{agent}} will then send system related logs and metrics to the {{ecloud}} deployment or project, where you can find pre-built system dashboards showing the health and performance of your virtual machines. + +:::{image} /deploy-manage/images/cloud-ec-marketplace-azure010.png +:alt: A dashboard showing system metrics for the VM +::: + +### Enable and disable VM extensions + +To enable or disable a VM extension: + +1. In Azure, navigate to your {{es}} deployment or project. +2. Select the **Virtual machines** tab. +3. Select one or more virtual machines. +4. Choose **Install Extension** or **Uninstall Extension**. + +:::{image} /deploy-manage/images/cloud-ec-marketplace-azure011.png +:alt: The Virtual Machines page in Azure +::: + +While it's possible to enable or disable a VM extension directly from the VM itself, we recommend always enabling or disabling your {{es}} VM extensions from within the context of your {{es}} deployment or project. + +### Manage the {{agent}} VM extension + +Once installed on the virtual machine, you can manage {{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 {{agent}}, check [Manage your {{agents}}](/reference/fleet/install-elastic-agents.md). + +### Operating system compatibility + +The Azure {{agent}} VM extension is supported on the following operating systems: + +| **Platform** | **Version** | +| --- | --- | +| Windows | 2008r2+ | +| CentOS | 6.10+ | +| Debian | 9,10 | +| Oracle | 6.8+ | +| RHEL | 7+ | +| Ubuntu | 16+ | diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service-troubleshooting.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service-troubleshooting.md new file mode 100644 index 0000000000..63588becd6 --- /dev/null +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service-troubleshooting.md @@ -0,0 +1,104 @@ +--- +applies_to: + deployment: + ess: ga + serverless: ga +products: + - id: cloud-hosted + - id: cloud-serverless +navigation_title: Troubleshooting +--- + +# Azure Native ISV Service troubleshooting + +$$$ec-azure-integration-troubleshooting$$$ + +This page describes some scenarios that you might experience onboarding to {{ecloud}} through the Azure console. If you're running into issues, you can always [get support](#azure-integration-support). + + +## Authorization errors + +When trying to access {{ecloud}} resources, you might get an error message indicating that the user must have the required authorization. + +:::{image} /deploy-manage/images/cloud-ec-marketplace-azure026.png +:alt: Error message displayed in the {{ecloud}} console: To access the resource {resource-name} +::: + +Elastic is not currently integrated with Azure user management, so sharing {{ecloud}} resources through the Cloud console with other Azure users is not possible. However, sharing direct access to these resources is possible. For details, refer to [Azure user management](/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md#azure-integration-multiple-users). + + +## Deployment creation failure [azure-integration-deployment-failed-network-security] + +When creating a new {{ecloud}} deployment or project, the resource creation might fail with a `Your deployment failed` error. The process results with a status message such as: + +```txt +{ + "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 resource creation failure is the default network security policies. Deployments or projects fail to create if a previously created network security policy has enabled the **Apply to future resources by default** option. When this option is enabled, traffic to the deployment or project is blocked, including traffic that is part of the {{ecloud}} Azure Native ISV Service. As a result, some of the integration components are not successfully provisioned and the deployment or project creation fails. + +Follow these steps to resolve the problem: + +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. Go to the [Network security page](https://cloud.elastic.co/access-security/network-security). +3. Edit the policy and disable the **Apply to future resources by default** option. +4. In Azure, create a new {{ecloud}} resource. +5. After the deployment has been created successfully, go back to the [Network security page](https://cloud.elastic.co/access-security/network-security) in {{ecloud}} and re-enable the **Apply to future resources by default** option. + +If your resource still does not create successfully, [contact the Elastic Support Team](#azure-integration-support) for assistance. + + +$$$azure-integration-failed-sso$$$ + +## SSO failures + +When you try to access your {{ecloud}} deployment or project using single sign-on, the access might 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](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-user-consent?tabs=azure-portal). To resolve this problem, contact your Azure Administrator. + + +$$$azure-integration-cant-see-deployment$$$ + +## Deployments or projects not visible in Azure Portal + +Elastic resources created using the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), the [{{es}} Service API](cloud://reference/cloud-hosted/ec-api-restful.md), or the [{{ecloud}} Terraform provider](https://registry.terraform.io/providers/elastic/ec/latest/docs) are only visible through the {{ecloud}} Console. To have the necessary metadata to be visible in the Azure Portal, {{ecloud}} resources need to be created in Microsoft Azure. + +::::{note} +Mimicking this metadata by manually adding tags to an {{ecloud}} deployment will not work around this limitation. Instead, it will prevent you from being able to delete the deployment using the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +:::: + + +$$$azure-integration-logs-not-ingested$$$ + +## Logs not being ingested + +* When you set up monitoring for your Azure services, if your Azure and Elastic resources are in different subscriptions, you need to make sure that the `Microsoft.Elastic` resource provider is registered in the subscription in which the Azure resources exist. Check [Configure log ingestion](azure-native-isv-service-logs-metrics.md#configure-log-ingestion) for details. +* If you are using [network security policies](/deploy-manage/security/network-security.md), reach out to [the Elastic Support Team](#azure-integration-support). + + +$$$azure-integration-support$$$ +$$$ec-getting-support$$$ + +## Get support [azure-integration-support] + +Support is provided by Elastic. To open a support case: + +1. Navigate to the [resource overview page](https://portal.azure.com/#browse/Microsoft.Elastic%2Fmonitors) in the Azure console. +2. Click **New support request** from the menu. +3. Click the link to open the {{ecloud}} console and provide further details. + + The Elastic Support team responds based on the SLA response time of your subscription. + + :::{image} /deploy-manage/images/cloud-ec-marketplace-azure005.png + :alt: The New Support Request page in Azure + ::: + +In case your {{ecloud}} 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`. diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md index a0e5bcc813..548f57cbfc 100644 --- a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md @@ -4,9 +4,10 @@ mapped_pages: applies_to: deployment: ess: ga - serverless: preview + serverless: ga products: - id: cloud-hosted + - id: cloud-serverless --- # Azure Native ISV Service [ec-azure-marketplace-native] @@ -19,528 +20,268 @@ The {{ecloud}} Azure Native ISV Service allows you to deploy managed instances o * **Integrated billing** - You are billed directly to your Azure account; no need to configure billing details in Elastic. See [Integrated billing](#ec-azure-integration-billing-summary) for details, as well as the [Billing FAQ](#ec-azure-integration-billing-faq). + You are billed directly to your Azure account; no need to configure billing details in Elastic. See [Integrated billing](#ec-azure-integration-billing-summary) for details. * **Easy consolidation of your Azure logs in Elastic** - Use a single-step setup to ingest logs from your Azure services into the {{stack}}. - + Use a single-step setup to ingest logs from your Azure services into the {{stack}}. For details, refer to [Azure Native ISV Service logs and metrics](azure-native-isv-service-logs-metrics.md). ::::{tip} The full product name in the Azure integrated marketplace is _{{ecloud}} (Elasticsearch) - An Azure Native ISV Service_. :::: +$$$ec-azure-integration-faq$$$ +## Prerequisites [azure-integration-get-started] -## Integrated billing [ec-azure-integration-billing-summary] - -Azure Native ISV Service includes integrated billing: Elastic resource costs are posted to your Azure subscription through the Microsoft Commercial Marketplace. You can create various {{ecloud}} resources (deployments) across different Azure subscriptions, with all of the costs associated with an {{ecloud}} organization posted to a single Azure subscription. - -Note the following terms: - -* **Azure Marketplace SaaS ID**: This is a unique identifier that’s generated one time by Microsoft Commercial Marketplace when a user creates their first Elastic resource (deployment) using the Microsoft Azure (Portal, API, SDK, or Terraform). This is mapped to a User ID and Azure Subscription ID -* **{{ecloud}} organization**: An [organization](../../users-roles/cloud-organization.md) is the foundational construct under which everything in {{ecloud}} is grouped and managed. An organization is created as a step during the creation of your first Elastic resource (deployment), whether that’s done through Microsoft Azure (Portal, API, SDK, or Terraform). The initial member of the {{ecloud}} organization can then invite other users. -* **Elastic resource (deployment)**: An {{ecloud}} deployment helps you manage an {{es}} cluster and instances of other Elastic products in one place. You can work with Elastic deployments from within the Azure ecosystem. Multiple users in the {{ecloud}} organization can create different deployments from different Azure subscriptions. They can also create deployments from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - -The following diagram shows the mapping between Microsoft Azure IDs, {{ecloud}} organization IDs, and your Elastic resources (deployments). - -:::{image} /deploy-manage/images/cloud-ec-azure-billing-mapping.png -:alt: Azure to {{ecloud}} mappings -::: - -The following diagram shows how your {{ecloud}} organization costs are reported in Microsoft Azure. You can also refer to our [Billing FAQ](#ec-azure-integration-billing-faq) on this page. - -:::{image} /deploy-manage/images/cloud-ec-azure-billing-reporting.png -:alt: Azure to {{ecloud}} mappings -::: - - -## Frequently asked questions [ec-azure-integration-faq] - -Check the following sections to learn more about the Azure Native ISV Service: - -* **Getting started** - - * [How do I get started?](#azure-integration-get-started) - * [What is the pricing for this offer?](#azure-integration-pricing) - * [Which Azure regions are supported?](#azure-integration-regions) - * [Which {{ecloud}} subscription levels are available?](#azure-integration-subscription-levels) - * [How can I change my {{ecloud}} subscription level?](#azure-integration-change-subscription) - * [Can I subscribe using an email address from another Elastic account?](#azure-integration-existing-email) - * [Is the {{ecloud}} Azure Native ISV Service connected with Azure user management?](#azure-integration-azure-user-management) - * [Does {{ecloud}} Azure Native ISV Service support recently introduced {{ecloud}} RBAC capability?](#azure-integration-azure-rbac) - * [I already have an {{ecloud}} account, can I use this service?](#azure-integration-prior-cloud-account) - * [Can I sign up for an {{ecloud}} trial account and then convert to the {{ecloud}} Azure Native ISV Service?](#azure-integration-convert-trial) - * [Can I sign up for an {{ecloud}} trial directly from the Azure marketplace?](#azure-integration-native-trials) - * [Does {{es}} get deployed into my tenant in Azure?](#azure-integration-azure-tenant) - * [What Azure tenant information does Elastic have access to?](#azure-integration-azure-tenant-info) - * [What other methods are available to deploy {{es}}?](#azure-integration-cli-api) - * [How do I migrate my data from the classic Azure marketplace account to the {{ecloud}} Azure Native ISV Service?](#azure-integration-migrate) - * [Can multiple Azure users deploy to the same {{ecloud}} organization?](#azure-integration-multiple-users) - * [Can I invite users to my organization, even if they cannot receive emails?](#azure-integration-no-inbox) - -* **Billing** - - * [Which Azure Subscription will be billed for my Elastic resources?](#azure-integration-billing-which-subscription) - * [How do I get different Elastic resources (deployments) charges to different Azure Subscriptions?](#azure-integration-billing-different-deployments) - * [How can I resubscribe to an {{ecloud}} Azure subscription](#azure-resubscribe-flow) - * [Why can’t I see Elastic resources costs in Azure Cost Explorer?](#azure-integration-billing-elastic-costs) - * [Why don’t I see my individual Elastic resources (deployments) in the Azure Marketplace Invoice?](#azure-integration-billing-deployments) - * [Why can’t I find Instance ID and Instance Name values from Azure Marketplace Invoice in the Azure Portal?](#azure-integration-billing-instance-values) - -* **Managing your {{ecloud}} deployment** - - * [What is included in my {{ecloud}} deployment?](#azure-integration-whats-included) - * [How can I access my {{ecloud}} deployment?](#azure-integration-how-to-access) - * [How can I modify my {{ecloud}} deployment?](#azure-integration-modify-deployment) - * [How can I delete my {{ecloud}} deployment?](#azure-integration-delete-deployment) - * [Can I delete the Azure Resource Group containing my deployment?](#azure-integration-delete-resource-group) - -* **Configuring logs and metrics** - - * [How do I monitor my existing Azure services?](#azure-integration-monitor) - * [How do I ingest metrics from my Azure services?](#azure-integration-ingest-metrics) - * [How can I monitor my Azure virtual machines in {{es}}?](#azure-integration-vm-extensions) - -* **Troubleshooting** - - * [I receive an error message about not having required authorization.](#azure-integration-authorization-access) - * [My {{ecloud}} deployment creation failed.](#azure-integration-deployment-failed-network-security) - * [I can’t SSO into my {{ecloud}} deployment.](#azure-integration-failed-sso) - * [I see some deployments in the {{ecloud}} console but not in the Azure Portal.](#azure-integration-cant-see-deployment) - * [My {{ecloud}} Azure Native ISV Service logs are not being ingested.](#azure-integration-logs-not-ingested) - -* **Support** - - * [How do I get support?](#azure-integration-support) - * [How can I change my subscription level / support level?](#azure-integration-change-level) - - - -## Getting started [ec-azure-integration-getting-started] - -$$$azure-integration-get-started$$$How do I get started with {{ecloud}}? -: {{ecloud}} is available as an offering through the Azure console. - - **Prerequisites** - - There are a few requirements to check before setting up an {{ecloud}} deployment: - - * In Azure your account role for the subscription is set as *Owner* or *Contributor*. For details and steps to assign roles, check [Permission to purchase](https://docs.microsoft.com/en-us/marketplace/azure-purchasing-invoicing#permission-to-purchase) in the Azure documentation. - * You cannot use an email address that already has an {{ecloud}} account. Use a different Azure account to set up the {{es}} resource, or [contact the Elastic Support Team](#azure-integration-support) for assistance. - * You must have a credit card registered on your Azure subscription. If you have a non-payment subscription, such as a [Virtual Studio Subscription](https://visualstudio.microsoft.com/subscriptions/), you can’t create an {{ecloud}} deployment. Refer to the Azure [Purchase errors](https://docs.microsoft.com/en-us/azure/partner-solutions/elastic/troubleshoot#purchase-errors) troubleshooting documentation for more information. - * In order to single sign-on into your {{ecloud}} deployment from Azure you need to request approval from your Azure administrator. - - **Getting started** - - To create a deployment directly from the Azure portal, go to [the list of {{ecloud}} deployments in the Azure portal](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Elastic%2Fmonitors) and select `Create`. - - When you create an {{ecloud}} deployment, an {{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 {{stack}}. Check our [Version policy](available-stack-versions.md) to learn more about when new versions are made available and old versions are removed from service. - - -$$$azure-integration-pricing$$$What is the pricing for this offer? -: Pricing is pay-as-you-go per hour for each {{ecloud}} 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 {{ecloud}} [Pricing Calculator](https://www.elastic.co/cloud/elasticsearch-service/pricing?page=docs&placement=docs-body) to size a deployment and view the corresponding hourly rate. - - Elastic charges include: - - * [Hourly consumption based on your active deployments](https://cloud.elastic.co/pricing) - * [Data transfer and snapshot storage charges](https://cloud.elastic.co/deployment-pricing-table) - - -$$$azure-integration-regions$$$Which Azure regions are supported? -: Here is the [list of available Azure regions](cloud://reference/cloud-hosted/ec-regions-templates-instances.md#ec-azure_regions) supported in {{ecloud}}. - -$$$azure-integration-subscription-levels$$$Which {{ecloud}} subscription levels are available? -: The subscription defaults to the Enterprise subscription, granting immediate access to advanced {{stack}} features like machine learning, and premium support response time SLAs. {{ecloud}} offers a number of different [subscription levels](https://elastic.co/pricing). - -$$$azure-integration-change-subscription$$$How can I change my {{ecloud}} subscription level? -: Modify your subscription level on the billing page in the Elastic console. - - 1. Select a deployment to open the deployment overview page. - 2. Select the **Advanced Settings** link to access your deployment in the {{ecloud}} console. - 3. In the {{ecloud}} console, select your account avatar icon at the top of the page, and then choose **Account & Billing**. - 4. Select the **Billing** tab and choose **Change my subscription**. - - :::{image} /deploy-manage/images/cloud-ec-marketplace-azure009.png - :alt: The Elastic Account Billing page with Advanced Settings highlighted - ::: - - 5. Select the [subscription level](https://elastic.co/pricing) that you’d like. - - :::{image} /deploy-manage/images/cloud-ec-marketplace-azure006.png - :alt: The Update Subscription page showing Standard - ::: - -$$$azure-integration-existing-email$$$Can I subscribe using an email address from another Elastic account? -: Your email address is associated with only one Elastic account. For a workaround, check [Sign up using an email address from another Cloud account](create-an-organization.md). - -$$$azure-integration-azure-user-management$$$Is the {{ecloud}} Azure Native ISV Service connected with Azure user management? -: No. Elastic is not currently integrated with Azure user management. Azure users who deploy {{es}} 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 {{es}}, {{kib}}, or APM in a deployment that was created by another Azure user, the following error is shown: - - :::{image} /deploy-manage/images/cloud-ec-marketplace-azure026.png - :alt: Error message displayed in the {{ecloud}} console: To access the resource {resource-name} - ::: - - Share deployment resources directly with other Azure users by [configuring Active Directory single sign-on with the {{es}} cluster](/deploy-manage/users-roles/cluster-or-deployment-auth/oidc-examples.md#ec-securing-oidc-azure). - - -$$$azure-integration-azure-rbac$$$Does {{ecloud}} Azure Native ISV Service support recently introduced {{ecloud}} RBAC capability? -: Yes. Currently [{{ecloud}} RBAC capability](../../users-roles/cloud-organization/user-roles.md) is available only from the {{ecloud}} Console and is not integrated with Azure Portal. This means that the users who will interact with Elastic resources from Azure Portal will not be recognized by the {{ecloud}} RBAC policies. - -$$$azure-integration-prior-cloud-account$$$I already have an {{ecloud}} account, can I use this service? -: Yes. If you already have an {{ecloud}} account with the same email address as your Azure account you may need to contact `support@elastic.co`. - -$$$azure-integration-convert-trial$$$Can I sign up for an {{ecloud}} trial account and then convert to the {{ecloud}} Azure Native ISV Service? -: Yes. You can start a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body) and then convert your account over to Azure. There are a few requirements: - - * Make sure when creating deployments in the trial account you specify Azure as the cloud provider. - * To convert your trial to the Azure marketplace you need to create a deployment in the Azure console. Just delete the new deployment if you don’t need it. After you create the new deployment your marketplace subscription is ready. - * Any deployments created during your trial won’t show up in the Azure console, since they weren’t created in Azure, but they are still accessible through the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and you are billed for their usage. - -$$$azure-integration-native-trials$$$Can I sign up for an {{ecloud}} trial directly from the Azure marketplace? -: Yes. You can start a 7-day trial by creating a deployment through the Azure Marketplace. The following restrictions apply: - - * The email associated with the Azure account used to create the deployment must not already be linked to an existing Elastic organization. - * During the 7-day trial period, you can create up to one deployment and three serverless projects. If you want to convert to a paid subscription before the end of the trial period, contact `support@elastic.co`. - * After 7 days, the trial will automatically convert to a paid offering. You can contact Elastic Support to unsubscribe, but doing so may result in your resources being deleted after a grace period. - * You can sign up for only one trial per user account. After the trial expires, you can't start another trial. If you need a trial extension, reach out to Elastic Support. - -$$$azure-integration-azure-tenant$$$Does {{es}} get deployed into my tenant in Azure? -: No. {{es}} resources deployed in an Azure tenant are managed by Elastic. The management capabilities associated with this tenant are the same as used to run Elastic’s managed service, which also allows users to deploy on Azure. - -$$$azure-integration-azure-tenant-info$$$What Azure tenant information does Elastic have access to? -: After you subscribe to {{ecloud}} through the Azure Native ISV Service, Elastic has access to the following Azure tenant information: - - * Data defined in the marketplace [Saas fulfillment Subscription APIs](https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api). - * The following additional data: - * Marketplace subscription ID - * Marketplace plan ID - * Azure Account ID - * Azure Tenant ID - * Company - * First name - * Last name - * Country - - - Elastic can also access data from {{ecloud}} Azure Native ISV Service features, including [resource and activity log data](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/platform-logs-overview). This data is available to Elastic only if you enable it. By default, Elastic does not have access to this information. - - -$$$azure-integration-cli-api$$$What other methods are available to deploy {{es}}? -: Use any of the following methods: - - * **Deploy using Azure tools** - * The Azure console - * [Azure Terraform](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/elastic_cloud_elasticsearch) - * The [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/elastic?view=azure-cli-latest) - * The Azure [REST API](https://docs.microsoft.com/en-us/rest/api/elastic) - * [PowerShell](https://docs.microsoft.com/en-us/powershell/module/az.elastic/?view=azps-8.0.0#elastic) - - * **Deploy using official Azure SDKs** - * [Python](https://github.com/Azure/azure-sdk-for-python/blob/main/README.md) - * [Java](https://github.com/Azure/azure-sdk-for-java/blob/azure-resourcemanager-elastic_1.0.0-beta.1/README.md) - * [.NET](https://github.com/Azure/azure-sdk-for-net/blob/main/README.md) - * [Rust](https://github.com/Azure/azure-sdk-for-rust/blob/main/services/README.md) - - * **Deploy using {{ecloud}}** - * The {{ecloud}} [console](https://cloud.elastic.co?page=docs&placement=docs-body) - * The {{ecloud}} [REST API](cloud://reference/cloud-hosted/ec-api-restful.md) - * The {{ecloud}} [command line tool](ecctl://reference/index.md) - * The {{ecloud}} [Terraform provider](https://registry.terraform.io/providers/elastic/ec/latest/docs) - - Note that when you use any of the {{ecloud}} methods, the {{es}} deployment will not be available in Azure. - - -$$$azure-integration-migrate$$$How do I migrate my data from the classic Azure marketplace account to the native integration? -: First create a new account configured with {{ecloud}} Azure Native ISV Service, then perform the migration as follows: - 1. From your classic Azure marketplace account, navigate to the deployment and [configure a custom snapshot repository using Azure Blog Storage](../../tools/snapshot-and-restore/ec-azure-snapshotting.md). - 2. Using the newly configured snapshot repository, [create a snapshot](../../tools/snapshot-and-restore/create-snapshots.md) of the data to migrate. - 3. Navigate to Azure and log in as the user that manages the {{es}} resources. - 4. Before proceeding, ensure the new account is configured according to the [prerequisites](#azure-integration-get-started). - 5. Create a [new {{es}} resource](#azure-integration-get-started) for each existing deployment that needs migration from the classic Azure account. - 6. In the new {{es}} resource, follow the steps in [Restore from a snapshot](../../../manage-data/migrate.md#ec-restore-snapshots) to register the custom snapshot repository from Step 1. - 7. In the same set of steps, restore the snapshot data from the snapshot repository that you registered. - 8. Confirm the data has moved successfully into your new {{es}} resource on Azure. - 9. To remove the old Azure subscription and the old deployments, go to the [Azure SaaS page](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.SaaS%2Fresources) and unsubscribe from the {{ecloud}} ({{es}}) marketplace subscription. This action triggers the existing deployments termination. - -$$$azure-integration-multiple-users$$$Can multiple Azure users deploy to the same {{ecloud}} organization? -: Yes! Before another user creates a native resource from the Azure Portal, invite them to your {{ecloud}} organization at [https://cloud.elastic.co/account/members](https://cloud.elastic.co/account/members). When they create the resource, it will get added to the existing organization instead of creating a new one, and allow you to benefit from consolidated billing, RBAC, and other benefits of an {{ecloud}} organization. - - -$$$azure-integration-no-inbox$$$Can I invite users to my organization, even if they cannot receive emails? -: You can add Azure users as members of your organization even if they don’t have an inbox. Reach out to Elastic support. - +$$$azure-integration-regions$$$ +$$$azure-integration-existing-email$$$ +$$$ec-supported-regions$$$ -## Billing [ec-azure-integration-billing-faq] +Before setting up an {{ecloud}} deployment or project through the Azure Native ISV Service, review the following requirements: -$$$azure-integration-billing-which-subscription$$$Which Azure Subscription will be billed for my Elastic resources? -: The Azure Marketplace integrated billing posts all of the Elastic deployment/resources costs related to an {{ecloud}} organization to the Azure subscription you used to create your first-ever Elastic deployment/resource. This is the case even if your individual Elastic resources (deployments) are spread across different Azure subscriptions. For more detail, refer to [Integrated billing](#ec-azure-integration-billing-summary). +* Your Azure account role for the subscription must be set to **Owner** or **Contributor**. For details and steps to assign roles, refer to [Roles and permissions](https://learn.microsoft.com/en-us/marketplace/roles-permissions#roles-and-permissions-1) in the Azure documentation. +* You can't use an email address that already has an {{ecloud}} account. Use a different Azure account to set up the {{es}} resource, or [contact Elastic Support](azure-native-isv-service-troubleshooting.md#azure-integration-support) for assistance. For a workaround, refer to [Sign up using an existing email address](//cloud-account/update-your-email-address.md#sign-up-existing). +* You must have a credit card registered on your Azure subscription. If you have a non-payment subscription, such as a [Virtual Studio Subscription](https://visualstudio.microsoft.com/subscriptions/), you can't create an {{ecloud}} deployment. Refer to the Azure [Purchase errors](https://learn.microsoft.com/en-us/azure/partner-solutions/elastic/troubleshoot#marketplace-purchase-errors) troubleshooting documentation for more information. +* To single sign-on into your {{ecloud}} deployment or project from Azure, you need to request approval from your Azure administrator. -$$$azure-integration-billing-different-deployments$$$How do I get different Elastic deployment/resources charges to different Azure Subscriptions? -: See [Integrated billing](#ec-azure-integration-billing-summary). To have different Elastic deployment/resources costs reported to different Azure subscriptions, they need to be in separate {{ecloud}} organizations. To create a separate {{ecloud}} organization from an Azure subscription, you will need to subscribe as a user who is not already part of an existing {{ecloud}} organization. +## Create a deployment or {{serverless-short}} project [ec-azure-integration-getting-started] -$$$azure-resubscribe-flow$$$How can I resubscribe to an {{ecloud}} Azure subscription? -: If your organization is currently unsubscribed from the Azure Marketplace, you can resubscribe through any of your existing Azure deployments in the Azure Portal: +To create a deployment or {{serverless-short}} project directly from the Azure portal, go to [the list of {{ecloud}} resources in the Azure portal](https://portal.azure.com/#browse/Microsoft.Elastic%2Fmonitors) and select **Create**. On the next page, select your hosting type: **{{serverless-short}}** or **Cloud Hosted**. - 1. Open one of your deployments to view its overview page. - 2. From the left navigation pane, select **Connected Elastic Cloud Resources**. +The selected resource is created for you. - :::{image} /deploy-manage/images/azure-reconnect-window.png - :alt: The resubscription illustration - ::: +If you select **{{serverless-short}}**, then the project is [sized automatically for you](/deploy-manage/deploy/elastic-cloud/serverless.md#_benefits_of_serverless_projects) and adjusts to your usage. - 3. Click **Resubscribe**. A new window should appear. - 4. Choose the subscription you want to resubscribe to and confirm. +If you select **Cloud Hosted**, a deployment is created with **16GB of RAM** and **560GB of storage**, across **two availability zones** for redundancy. The size of the deployment, both RAM and storage, can be changed [directly in the {{ecloud}} console](/deploy-manage/deploy/elastic-cloud/configure.md). Usage charges are based on the deployment size, so size your instance efficiently. The deployment defaults to the latest available version of the {{stack}}. Check our [Version policy](available-stack-versions.md) to learn more about when new versions are made available and old versions are removed from service. -$$$azure-integration-billing-elastic-costs$$$Why can’t I see Elastic resources costs in Azure Cost Explorer? -: The costs associated with Elastic resources (deployments) are reported under unassigned in the Azure Portal. Refer to [Understand your Azure external services charges](https://learn.microsoft.com/en-us/azure/cost-management-billing/understand/understand-azure-marketplace-charges) in the Microsoft Documentation to understand Elastic resources/deployments costs. For granular Elastic resources costs, refer to [Monitor and analyze your account usage](../../cloud-organization/billing/monitor-analyze-usage.md). +### Alternative creation methods [azure-integration-cli-api] -$$$azure-integration-billing-deployments$$$Why don’t I see my individual Elastic resources (deployments) in the Azure Marketplace Invoice? -: The way Azure Marketplace Billing Integration works today, the costs for Elastic resources (deployments) are reported for an {{ecloud}} 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 [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) in the respective {{ecloud}} organization. For granular Elastic resources costs refer to [Monitor and analyze your account usage](../../cloud-organization/billing/monitor-analyze-usage.md). As well, for more detail refer to [Integrated billing](#ec-azure-integration-billing-summary). +You can create and manage {{ecloud}} deployments and projects using a variety of tools: - :::{image} /deploy-manage/images/cloud-ec-azure-billing-example.png - :alt: Example billing report in the {{ecloud}} console - ::: +* **Azure tools** + * The Azure console + * [Azure Terraform](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/elastic_cloud_elasticsearch) + * The [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/elastic?view=azure-cli-latest) + * The Azure [REST API](https://docs.microsoft.com/en-us/rest/api/elastic) + * [PowerShell](https://docs.microsoft.com/en-us/powershell/module/az.elastic/?view=azps-8.0.0#elastic) +* **Official Azure SDKs** + * [Python](https://github.com/Azure/azure-sdk-for-python/blob/main/README.md) + * [Java](https://github.com/Azure/azure-sdk-for-java/blob/azure-resourcemanager-elastic_1.0.0-beta.1/README.md) + * [.NET](https://github.com/Azure/azure-sdk-for-net/blob/main/README.md) + * [Rust](https://github.com/Azure/azure-sdk-for-rust/blob/main/services/README.md) -$$$azure-integration-billing-instance-values$$$Why can’t I find Instance ID and Instance Name values from Azure Marketplace Invoice in the Azure Portal? -: With {{ecloud}} Azure Native ISV Service, the "instance name/ID" shown in the Azure Marketplace invoice is the Azure Marketplace SaaS identifier that represents an {{ecloud}} organization. For Microsoft Azure, `Microsoft.SaaS` (namespace) resources are used for billing Marketplace Resources - in this case, Elastic. +* **{{ecloud}}** + * The {{ecloud}} [console](https://cloud.elastic.co?page=docs&placement=docs-body) + * The {{ecloud}} [REST API](cloud://reference/cloud-hosted/ec-api-restful.md) + * The {{ecloud}} [command line tool](ecctl://reference/index.md) (ECCTL) + * The {{ecloud}} [Terraform provider](https://registry.terraform.io/providers/elastic/ec/latest/docs) + + Refer to [Tools and APIs](/deploy-manage/deploy/elastic-cloud/tools-apis.md) for a complete list. - 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 {{ecloud}} organization and not individual Elastic resources (deployments). To see the cost breakdown for individual Elastic resources (deployments), refer to [Monitor and analyze your account usage](../../cloud-organization/billing/monitor-analyze-usage.md). - - :::{image} /deploy-manage/images/cloud-ec-azure-missing-instance-id.png - :alt: Instance ID not found error in Azure console + :::{note} + When you use any of the {{ecloud}} methods to create a deployment or project, it will not be available in the Azure Portal. To have the necessary metadata to be visible in the Azure Portal, {{ecloud}} resources need to be created in Microsoft Azure. ::: +## Access your deployment or project [azure-integration-how-to-access] +$$$azure-integration-whats-included$$$ +$$$azure-integration-modify-deployment$$$ +$$$ec-azure-integration-managing-deployment$$$ -## Managing your {{ecloud}} deployment [ec-azure-integration-managing-deployment] +Navigate to the [{{ecloud}} overview page](https://portal.azure.com/#browse/Microsoft.Elastic%2Fmonitors) in the Azure portal and select a resource. -$$$azure-integration-whats-included$$$What is included in my {{ecloud}} deployment? -: Each {{ecloud}} deployment includes: +You have a few options to access your deployment or project: - * An {{es}} cluster - * A {{kib}} instance which provides data visualization and a front-end for the {{stack}} - * An APM server that allows you to easily collect application traces +* **{{es}} endpoint** -- the URL for communicating with {{es}} directly +* **{{kib}} endpoint** -- the UI for your deployment or project, a great way for new users to get started +* **{{ecloud}}** -- Open the **Advanced Settings** link to access the deployment or project in the {{ecloud}} console. You can use this interface to alter your deployment or project settings, or perform other administrative tasks. For more details, refer to the following sections: + * [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md#ec_how_to_operate_elasticsearch_service) + * [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md#get-started) -$$$azure-integration-how-to-access$$$How can I access my {{ecloud}} deployment? -: Navigate to the deployment overview page in Azure: +## Trials and existing accounts [ec-azure-integration-trials] +% needs to be updated for multi org - Select a deployment to open the deployment overview page. +$$$azure-integration-prior-cloud-account$$$ +If you already have an {{ecloud}} account with the same email address as your Azure account, you might need to contact `support@elastic.co`. - Then you have a few options to access your deployment: +### Convert a trial to Azure ISV [azure-integration-convert-trial] - * **{{es}} endpoint** - the URL for the {{es}} cluster itself - * **{{kib}} endpoint** - the UI for the {{stack}}, a great way for new users to get started - * **{{ecloud}}** - Open the **Advanced Settings** link to access the deployment in the {{ecloud}} console, to change the size of the deployment or upgrade it. +You can start a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body) and then convert your organization over to Azure. There are a few requirements: +* Make sure when creating resources in the trial account that you specify Azure as the cloud provider. +* To convert your trial to the Azure marketplace you need to [create a resource](/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md#ec-azure-integration-getting-started) in the Azure console. Delete this resource if you don't need it. After you create the new resource, your marketplace subscription is ready. +* Any resources created during your trial won't show up in the Azure console, because they weren't created in Azure, but they are still accessible through the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and you are billed for their usage. -$$$azure-integration-modify-deployment$$$How can I modify my {{ecloud}} deployment? -: Modify your {{ecloud}} deployment in the {{ecloud}} console, which is accessed from the Azure UI through the **Advanced Settings** link on the deployment overview page. In the {{ecloud}} console you can perform [a number of actions against your deployment](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md#ec_how_to_operate_elasticsearch_service). +### Start a trial from Azure Marketplace [azure-integration-native-trials] -$$$azure-integration-delete-deployment$$$How can I delete my {{ecloud}} deployment? -: Delete the deployment directly from the Azure console. The delete operation performs clean-up activities in the Elastic console to ensure any running components are removed, so that no additional charges occur. +You can start a 7-day trial by creating a deployment through the Azure Marketplace. The following restrictions apply: -$$$azure-integration-delete-resource-group$$$Can I delete the Azure Resource Group containing my deployment? -: If you delete an Azure Resource Group containing {{ecloud}} resources, the latter will be deleted automatically. However, you should not delete the Azure Resource Group containing the first deployment you created. The usage associated with any other Elastic deployment created outside of the first resource group will continue to get reported and charged against this resource group. If you want to stop all charges to this Resource Group, you should delete the individual deployments. +* The email associated with the Azure account used to create the deployment must not already be linked to an existing Elastic organization. +* During the 7-day trial period, you can create up to one deployment and three serverless projects. If you want to convert to a paid subscription before the end of the trial period, contact `support@elastic.co`. +* After 7 days, the trial will automatically convert to a paid offering. You can contact Elastic Support to unsubscribe, but doing so might result in your resources being deleted after a grace period. +* You can sign up for only one trial per user account. After the trial expires, you can't start another trial. If you need a trial extension, reach out to Elastic Support. +## Pricing [azure-integration-pricing] -## Configuring logs and metrics [ec-azure-logs-and-metrics] +$$$azure-integration-subscription-levels$$$ -$$$azure-integration-monitor$$$How do I monitor my existing Azure services? -: The {{ecloud}} Azure Native ISV Service simplifies logging for Azure services with the {{stack}}. This integration supports: +Pricing is pay-as-you-go per hour for each {{ecloud}} deployment or project created. Charges are applied to your Azure bill at the end of the month. - * Azure subscription logs - * Azure resources logs (check [Supported categories for Azure Resource Logs](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-categories?WT.mc_id=Portal-Azure_Marketplace_Elastic) for examples) +When you create your first deployment or project, the subscription defaults to the Enterprise subscription, which grants premium support response time SLAs. For {{ech}} deployments, the subscription also controls the features that are available. In {{ech}}, this Enterprise subscription includes advanced {{stack}} features like {{ml}}. +For an overview of all of the subscription levels available, refer to [subscription levels](https://elastic.co/pricing). To learn how to change your subscription level, refer to [](/deploy-manage/cloud-organization/billing/manage-subscription.md). -::::{note} -If you want to send platform logs to a deployment that has [network security policies](/deploy-manage/security/network-security.md) applied, then you need to contact [the Elastic Support Team](#azure-integration-support) to perform additional configurations. Refer support to the article [Azure++ Resource Logs blocked by Traffic Filters](https://support.elastic.co/knowledge/18603788). +To learn about Elastic charges related to your deployments or projects, refer to the following resources: +* [](/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md) +* [](/deploy-manage/cloud-organization/billing/serverless-project-billing-dimensions.md) +* [{{ecloud}} pricing table](https://cloud.elastic.co/cloud-pricing-table) -:::: +To estimate your costs, you can use the following calculators: +* [{{ech}} pricing calculator](https://cloud.elastic.co/pricing) +* [{{serverless-full}} pricing calculator](https://cloud.elastic.co/pricing/serverless) -The following log types are not supported as part of this integration: - -* Azure tenant logs -* Logs from Azure compute services, such as Virtual Machines - -::::{note} -If your Azure resources and Elastic deployment are in different subscriptions, before creating diagnostic settings confirm that the `Microsoft.Elastic` resource provider is registered in the subscription in which the Azure resources exist. If not, register the resource provider following these steps: +## Integrated billing [ec-azure-integration-billing-summary] -1. In Azure, navigate to **Subscriptions → Resource providers**. -2. Search for `Microsoft.Elastic` and check that it is registered. +Azure Native ISV Service includes integrated billing: Elastic resource costs are posted to your Azure subscription through the Microsoft Commercial Marketplace. You can create various {{ecloud}} resources (deployments and projects) across different Azure subscriptions, with all of the costs associated with an {{ecloud}} organization posted to a single Azure subscription. -If you already created diagnostic settings before the `Microsoft.Elastic` resource provider was registered, delete and add the diagnostic setting again. +The integrated billing process involves the following concepts: -:::: +* **Azure Marketplace SaaS ID**: This is a unique identifier that's generated one time by Microsoft Commercial Marketplace when a user creates their first Elastic resource (deployment or project) using the Microsoft Azure (Portal, API, SDK, or Terraform). This is mapped to a User ID and Azure Subscription ID. +* **{{ecloud}} organization**: An [organization](/deploy-manage/cloud-organization.md) is the foundational construct under which everything in {{ecloud}} is grouped and managed. An organization is created as a step during the creation of your first Elastic resource, whether that's done through Microsoft Azure (Portal, API, SDK, or Terraform). The initial member of the {{ecloud}} organization can then invite other users. +* **Elastic resource (deployment or project)**: An {{ecloud}} deployment or project helps you manage an {{es}} cluster and instances of other Elastic products in one place. You can work with Elastic resources from within the Azure ecosystem. Multiple users in the {{ecloud}} organization can create different resources from different Azure subscriptions. They can also create resources from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +The following diagram shows the mapping between Microsoft Azure IDs, {{ecloud}} organization IDs, and your Elastic resources (deployments). -In the Azure console, configure the ingestion of Azure logs into either a new or existing {{ecloud}} deployment: +% needs to be updated for multi org +:::{image} /deploy-manage/images/cloud-ec-azure-billing-mapping.png +:alt: Azure to {{ecloud}} mappings +::: -* When creating a new deployment, use the **Logs & metrics** tab in Azure to specify the log type and a key/value tag pair. Any Azure resources that match on the tag value automatically send log data to the {{ecloud}} deployment, once it’s been created. +The following diagram shows how your {{ecloud}} organization costs are reported in Microsoft Azure. -:::{image} /deploy-manage/images/cloud-ec-marketplace-azure004.png -:alt: The Logs & Metrics tab on the Create Elastic Resource page +:::{image} /deploy-manage/images/cloud-ec-azure-billing-reporting.png +:alt: Azure to {{ecloud}} mappings ::: -* For existing deployments configure Azure logs from the deployment overview page in the Azure console. +### Resubscribe to Azure [azure-resubscribe-flow] -::::{important} -Note that following restrictions for logging: +If your organization is currently unsubscribed from the Azure Marketplace, you can resubscribe through any of your existing Azure deployments in the Azure Portal: -* Only logs from non-compute Azure services are ingested as part of the configuration detailed in this document. Logs from compute services, such as Virtual Machines, into the {{stack}} will be added in a future release. +1. Open one of your deployments or projects to view its overview page. +2. From the left navigation pane, select **Connected Elastic Cloud Resources**. -* The Azure services must be in one of the [supported regions](cloud://reference/cloud-hosted/ec-regions-templates-instances.md#ec-azure_regions). All regions will be supported in the future. +:::{image} /deploy-manage/images/azure-reconnect-window.png +:alt: The resubscription illustration +::: -:::: +3. Click **Resubscribe**. A new window should appear. +4. Choose the subscription you want to resubscribe to and confirm. +### Cost visibility in Azure [ec-azure-integration-billing-faq] -::::{note} -Your Azure logs may sometimes contain references to a user `Liftr_Elastic`. This user is created automatically by Azure as part of the integration with {{ecloud}}. -:::: +#### Subscription used for billing [azure-integration-billing-which-subscription] -To check which of your Azure resources are currently being monitored, navigate to your {{es}} deployment and open the **Monitored resources** tab. Each resource shows one of the following status indicators: +$$$azure-integration-billing-which-subscription$$$ -* *Sending* - Logs are currently being sent to the {{es}} cluster. -* *Logs not configured* - Log collection is currently not configured for the resource. Open the **Edit tags** link to configure which logs are collected. For details about tagging resources, check [Use tags to organize your Azure resources and management hierarchy](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources?tabs=json) in the Azure documentation. -* *N/A* - Monitoring is not available for this resource type. -* *Limit reached* - Azure resources can send diagnostic data to a maximum of five outputs. Data is not being sent to the {{es}} cluster because the output limit has already been reached. -* *Failed* - Logs are configured but failed to ship to the {{es}} cluster. For help resolving this problem you can [contact Support](#azure-integration-support). -* *Region not supported* - The Azure resource must be in one of the [supported regions](#ec-supported-regions). +The Azure Marketplace integrated billing posts all of the Elastic resource costs related to an {{ecloud}} organization to the Azure subscription you used to create your first-ever Elastic resource, even if your individual Elastic resources (deployments and projects) are spread across different Azure subscriptions. -$$$azure-integration-ingest-metrics$$$How do I ingest metrics from my Azure services? -: Metrics are not supported as part of the current {{ecloud}} Azure Native ISV Service. This will be implemented in a future phase. Metrics can still be collected from all Azure services using Metricbeat. For details, check [Ingest other Azure metrics using the Metricbeat Azure module](../../../solutions/observability/cloud/monitor-microsoft-azure-with-beats.md#azure-step-four). +% needs to be updated for multi org +$$$azure-integration-billing-different-deployments$$$ +To have different Elastic resources' costs reported to different Azure subscriptions, they need to be in separate {{ecloud}} organizations. To create a separate {{ecloud}} organization from an Azure subscription, you will need to subscribe as a user who is not already part of an existing {{ecloud}} organization. -$$$azure-integration-vm-extensions$$$How can I monitor my Azure virtual machines in {{es}}? -: 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 {{ecloud}} cluster where you can find pre-built system dashboards showing the health and performance of your virtual machines. +#### How costs are reported - :::{image} /deploy-manage/images/cloud-ec-marketplace-azure010.png - :alt: A dashboard showing system metrics for the VM - ::: +$$$azure-integration-billing-elastic-costs$$$ - **Enabling and disabling VM extensions** +The costs associated with Elastic resources are reported under **unassigned** in the Azure Portal. Refer to [Understand your Azure external services charges](https://learn.microsoft.com/en-us/azure/cost-management-billing/understand/understand-azure-marketplace-charges) in the Microsoft Documentation to understand Elastic resource costs. For granular Elastic resource costs, refer to [Monitor and analyze your account usage](/deploy-manage/cloud-organization/billing/monitor-analyze-usage.md). - To enable or disable a VM extension: +$$$azure-integration-billing-deployments$$$ - 1. In Azure, navigate to your {{es}} deployment. - 2. Select the **Virtual machines** tab - 3. Select one or more virtual machines - 4. Choose **Install Extension** or **Uninstall Extension**. +The costs for Elastic resources are reported for an {{ecloud}} organization as a single line item, reported against the Marketplace SaaS ID. This includes the resources created using the Azure Portal, API, SDK, or CLI, and also those created directly from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) in the respective {{ecloud}} organization. - :::{image} /deploy-manage/images/cloud-ec-marketplace-azure011.png - :alt: The Virtual Machines page in Azure - ::: +$$$azure-integration-billing-instance-values$$$ - While it’s possible to enable or disable a VM extension directly from the VM itself, we recommend always enabling or disabling your {{es}} VM extensions from within the context of your {{es}} deployment. +#### Invoice values - **Managing the Elastic Agent VM extension** +* **Instance name/ID** The Azure Marketplace SaaS identifier that represents an {{ecloud}} organization. For Microsoft Azure, `Microsoft.SaaS` (namespace) resources are used for billing Marketplace Resources -- in this case, Elastic. - 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](/reference/fleet/install-elastic-agents.md). + 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`. - **Operating system compatibility matrix** +* `Microsoft.SaaS` (Instance name) asset is shown in the Azure Marketplace invoice and represents costs related to an {{ecloud}} organization and not individual Elastic resources. To understand the cost breakdown for individual Elastic resources, refer to [Monitor and analyze your account usage](../../cloud-organization/billing/monitor-analyze-usage.md). - The Azure Elastic Agent VM extension is supported on the following operating systems: +## Users and access [ec-azure-integration-users-access] - | **Platform** | **Version** | - | --- | --- | - | Windows | 2008r2+ | - | CentOS | 6.10+ | - | Debian | 9,10 | - | Oracle | 6.8+ | - | RHEL | 7+ | - | Ubuntu | 16+ | +[User access](/deploy-manage/users-roles.md#cloud-organization-level) is managed within the {{ecloud}} organization, or at the deployment level. +There are several options to integrate Microsoft authentication with {{ecloud}}: +* {{serverless-full}} projects and {{ech}} deployments: [Configure SAML single sign-on](/deploy-manage/users-roles/cloud-organization/configure-saml-authentication.md). Refer to [](/deploy-manage/users-roles/cloud-organization/register-elastic-cloud-saml-in-microsoft-entra-id.md) for a Microsoft Entra ID example. +* {{ech}} deployments: [Configure Azure Active Directory single sign-on](/deploy-manage/users-roles/cluster-or-deployment-auth/saml-entra.md). +{{ecloud}} is not automatically integrated with Azure: -## Troubleshooting [ec-azure-integration-troubleshooting] +* [{{ecloud}} RBAC capabilities](../../users-roles/cloud-organization/user-roles.md) are available only from the {{ecloud}} Console and is not integrated with Azure Portal. Users who interact with Elastic resources from Azure Portal will not be recognized by the {{ecloud}} RBAC policies. -This section describes some scenarios that you may experience onboarding to {{ecloud}} through the Azure console. If you’re running into issues you can always [get support](#azure-integration-support). +$$$azure-integration-authorization-access$$$ +* Elastic is not currently integrated with Azure user management. Azure users who deploy {{es}} 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. -$$$azure-integration-authorization-access$$$I receive an error message about not having the required authorization. -: When trying to access {{ecloud}} resources, you may get an error message indicating that *the user must have the required authorization.* + When trying to access resources such as {{es}}, {{kib}}, or {{product.apm}} in a deployment or project that was created by another Azure user, the following error is shown: :::{image} /deploy-manage/images/cloud-ec-marketplace-azure026.png :alt: Error message displayed in the {{ecloud}} console: To access the resource {resource-name} ::: - 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 {{ecloud}} Azure Native ISV Service connected with Azure user management?](#azure-integration-azure-user-management). - - -$$$azure-integration-deployment-failed-network-security$$$My {{ecloud}} deployment creation failed. -: When creating a new {{ecloud}} deployment, the deployment creation may fail with a `Your deployment failed` error. The process results with a status message such as: - - ```txt - { - "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." - } - ] - ``` +### Allow multiple users to create resources in an organization [azure-integration-multiple-users] - One possible cause of a deployment creation failure is the default network security policies. Deployments fail to create if a previously created network security policy 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 {{ecloud}} Azure Native ISV Service. As a result, some of the integration components are not successfully provisioned and the deployment creation fails. +$$$azure-integration-no-inbox$$$ - Follow these steps to resolve the problem: +Multiple Azure users can deploy to the same {{ecloud}} organization. Before another user creates a native resource from the Azure Portal, invite them to your {{ecloud}} organization at [https://cloud.elastic.co/account/members](https://cloud.elastic.co/account/members). When they create the resource, it will get added to the existing organization instead of creating a new one, allowing you to benefit from consolidated billing, RBAC, and other benefits of an {{ecloud}} organization. - 1. Login to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). - 2. Go to the [Network security page](https://cloud.elastic.co/deployment-features/traffic-filters). - 3. Edit the traffic filter and disable the **Include by default** option. - 4. In Azure, create a new {{ecloud}} deployment. - 5. After the deployment has been created successfully, go back to the [Network security page](https://cloud.elastic.co/deployment-features/traffic-filters) in {{ecloud}} and re-enable the **Include by default** option. +You can add Azure users as members of your organization even if they don't have an inbox. Reach out to Elastic support. +## Azure tenant information [azure-integration-azure-tenant] -If your deployment still does not create successfully, [contact the Elastic Support Team](#azure-integration-support) for assistance. +{{es}} resources deployed in an Azure tenant are managed by Elastic. The management capabilities associated with this tenant are the same as used to run Elastic's managed service, which also allows users to deploy on Azure. {{es}} is not deployed into your Azure tenant. -$$$azure-integration-failed-sso$$$I can’t SSO into my {{ecloud}} deployment. -: When you try to access your {{ecloud}} deployment using single sign-on, the access may fail due to missing permission required by your Azure environment. +$$$azure-integration-azure-tenant-info$$$ +After you subscribe to {{ecloud}} through the Azure Native ISV Service, Elastic has access to the following Azure tenant information: - You can review your user consent settings configuration following the instructions in [Configure how users consent to applications](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-user-consent?tabs=azure-portal). To resolve this problem, contact your Azure Administrator. - - -$$$azure-integration-cant-see-deployment$$$I see some deployments in the {{ecloud}} console but not in the Azure Portal. -: Elastic Deployments created using the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), the [{{es}} Service API](cloud://reference/cloud-hosted/ec-api-restful.md), or the [{{ecloud}} Terraform provider](https://registry.terraform.io/providers/elastic/ec/latest/docs) are only visible through the {{ecloud}} Console. To have the necessary metadata to be visible in the Azure Portal, {{ecloud}} deployments need to be created in Microsoft Azure. - -::::{note} -Mimicking this metadata by manually adding tags to an {{ecloud}} deployment will not work around this limitation. Instead, it will prevent you from being able to delete the deployment using the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -:::: +* Data defined in the marketplace [Saas fulfillment Subscription APIs](https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api). +* The following additional data: + * Marketplace subscription ID + * Marketplace plan ID + * Azure Account ID + * Azure Tenant ID + * Company + * First name + * Last name + * Country +Elastic can also access data from {{ecloud}} Azure Native ISV Service features, including [resource and activity log data](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/platform-logs-overview). This data is available to Elastic only if you enable it. By default, Elastic does not have access to this information. -$$$azure-integration-logs-not-ingested$$$My {{ecloud}} Azure Native ISV Service logs are not being ingested. -: * When you set up monitoring for your Azure services, if your Azure and Elastic resources are in different subscriptions, you need to make sure that the `Microsoft.Elastic` resource provider is registered in the subscription in which the Azure resources exist. Check [How do I monitor my existing Azure services?](#azure-integration-monitor) for details. -* If you are using [network security policies](/deploy-manage/security/network-security.md), reach out to [the Elastic Support Team](#azure-integration-support). +## Migrate from classic Azure marketplace [azure-integration-migrate] +First create a new account configured with {{ecloud}} Azure Native ISV Service, then perform the migration as follows: +1. From your classic Azure marketplace account, navigate to the deployment and [configure a custom snapshot repository using Azure Blob Storage](/deploy-manage/tools/snapshot-and-restore/ec-azure-snapshotting.md). +2. Using the newly configured snapshot repository, [create a snapshot](/deploy-manage/tools/snapshot-and-restore/create-snapshots.md) of the data to migrate. +3. Navigate to Azure and log in as the user that manages the {{es}} resources. +4. Before proceeding, ensure the new account is configured according to the [prerequisites](#azure-integration-get-started). +5. Create a [new {{es}} resource](#azure-integration-get-started) for each existing deployment that needs migration from the classic Azure account. +6. In the new {{es}} resource, follow the steps in [Restore from a snapshot](/manage-data/migrate.md#ec-restore-snapshots) to register the custom snapshot repository from Step 1. +7. In the same set of steps, restore the snapshot data from the snapshot repository that you registered. +8. Confirm the data has moved successfully into your new {{es}} resource on Azure. +9. To remove the old Azure subscription and the old deployments, go to the [Azure SaaS page](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.SaaS%2Fresources) and unsubscribe from the {{ecloud}} ({{es}}) marketplace subscription. This action triggers the existing deployments' termination. -## Getting support [ec-getting-support] -$$$azure-integration-support$$$How do I get support? -: Support is provided by Elastic. To open a support case: +## Delete a resource or Azure resource group [ec-azure-integration-delete] - 1. Navigate to the deployment overview page in the Azure console. - 2. Click **New support request** from the menu. - 3. Click the link to launch the Elastic console and provide further details. +$$$azure-integration-delete-deployment$$$ +Delete the deployment directly from the Azure console. The delete operation performs clean-up activities in the Elastic console to ensure any running components are removed, so that no additional charges occur. - The Elastic Support team responds based on the SLA response time of your subscription. +$$$azure-integration-delete-resource-group$$$ +If you delete an Azure Resource Group containing {{ecloud}} resources, the latter will be deleted automatically. However, you should not delete the Azure Resource Group containing the first deployment or project that you created. The usage associated with any other Elastic deployment created outside of the first resource group will continue to get reported and charged against this resource group. If you want to stop all charges to this Resource Group, you should delete the individual deployments. - :::{image} /deploy-manage/images/cloud-ec-marketplace-azure005.png - :alt: The New Support Request page in Azure - ::: - - - In case your {{ecloud}} 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`. - - -$$$azure-integration-change-level$$$How can I change my subscription level / support level? -: Your Elastic subscription level includes the support level. Check [How can I change my {{ecloud}} subscription level?](#azure-integration-change-subscription) to make an update. - - -$$$ec-supported-regions$$$ diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 42aaadc988..347bc9e73b 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -17,6 +17,9 @@ toc: - hidden: deploy/elastic-cloud/create-monthly-pay-as-you-go-subscription-on-gcp-marketplace.md - file: deploy/elastic-cloud/aws-marketplace.md - file: deploy/elastic-cloud/azure-native-isv-service.md + children: + - file: deploy/elastic-cloud/azure-native-isv-service-logs-metrics.md + - file: deploy/elastic-cloud/azure-native-isv-service-troubleshooting.md - file: deploy/elastic-cloud/google-cloud-platform-marketplace.md - file: deploy/elastic-cloud/heroku.md children: diff --git a/redirects.yml b/redirects.yml index c6a6cc0024..9c1104e53a 100644 --- a/redirects.yml +++ b/redirects.yml @@ -291,9 +291,25 @@ redirects: 'ec-restrictions-traffic-filters-kibana-sso': 'ec-restrictions-network-security-kibana-sso' 'ec-restrictions-traffic-filters-watcher': 'ec-restrictions-network-security-watcher' 'deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md': - to: 'deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md' - anchors: - 'azure-integration-deployment-failed-traffic-filter': 'azure-integration-deployment-failed-network-security' + anchors: {} + many: + - to: 'deploy-manage/deploy/elastic-cloud/azure-native-isv-service-troubleshooting.md' + anchors: + 'azure-integration-deployment-failed-traffic-filter': 'azure-integration-deployment-failed-network-security' + 'azure-integration-deployment-failed-network-security': 'azure-integration-deployment-failed-network-security' + 'azure-integration-authorization-access': 'authorization-errors' + 'azure-integration-failed-sso': 'azure-integration-failed-sso' + 'azure-integration-cant-see-deployment': 'azure-integration-cant-see-deployment' + 'azure-integration-logs-not-ingested': 'azure-integration-logs-not-ingested' + 'azure-integration-support': 'azure-integration-support' + 'ec-azure-integration-troubleshooting': 'ec-azure-integration-troubleshooting' + 'ec-getting-support': 'ec-getting-support' + - to: 'deploy-manage/deploy/elastic-cloud/azure-native-isv-service-logs-metrics.md' + anchors: + 'azure-integration-monitor': 'azure-integration-monitor' + 'azure-integration-ingest-metrics': 'azure-integration-ingest-metrics' + 'azure-integration-vm-extensions': 'azure-integration-vm-extensions' + 'ec-azure-logs-and-metrics': 'ec-azure-logs-and-metrics' 'deploy-manage/remote-clusters/ec-enable-ccs.md': to: 'deploy-manage/remote-clusters/ec-enable-ccs.md' anchors: From 2d9bef32732f41144539fb64c5644d5bced5ff08 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 8 Apr 2026 12:57:13 -0400 Subject: [PATCH 10/19] draft marketplace content --- .../billing/add-billing-details.md | 2 +- .../deploy/elastic-cloud/aws-marketplace.md | 4 +- .../elastic-cloud/azure-native-isv-service.md | 2 +- .../elastic-cloud/create-an-organization.md | 2 +- .../google-cloud-platform-marketplace.md | 2 + .../marketplace-trial-conversion.md | 75 +++++++++++++++++++ .../subscribe-from-marketplace.md | 26 ++++--- deploy-manage/toc.yml | 1 + 8 files changed, 98 insertions(+), 16 deletions(-) create mode 100644 deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md diff --git a/deploy-manage/cloud-organization/billing/add-billing-details.md b/deploy-manage/cloud-organization/billing/add-billing-details.md index fffa692020..0cba40e49f 100644 --- a/deploy-manage/cloud-organization/billing/add-billing-details.md +++ b/deploy-manage/cloud-organization/billing/add-billing-details.md @@ -13,7 +13,7 @@ products: If you want to use {{ecloud}} beyond the trial period or if you want to use features not included in the trial, then you need to add a credit card to your account. Your credit card information is sent securely to our [billing provider](http://recurly.com/security) and stored with them. -Alternatively, if you want to pay for {{ecloud}} together with other cloud services that you're already using, then you can subscribe to {{ecloud}} through a [marketplace](/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md). +Alternatively, if you want to pay for {{ecloud}} together with other cloud services that you're already using, then you can subscribe to {{ecloud}} through a [marketplace](/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md). If you already have an {{ecloud}} trial, you can [convert it to a marketplace subscription](/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md) to preserve your existing deployments and data. If you plan to use {{ech}}, then you can estimate how much your use case will cost using our [pricing calculator](https://www.elastic.co/cloud/elasticsearch-service/pricing). diff --git a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md index 985ac5d0e7..f46ac91814 100644 --- a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md @@ -7,6 +7,7 @@ applies_to: serverless: ga products: - id: cloud-hosted + - id: cloud-serverless --- # AWS Marketplace [ec-billing-aws] @@ -20,10 +21,11 @@ The free trial includes provisioning of a single deployment and you are not char You can subscribe to {{ecloud}} directly from the AWS Marketplace. You then have the convenience of viewing your {{ecloud}} subscription as part of your AWS bill, and you do not have to supply any additional billing information to Elastic. +If you already have an {{ecloud}} trial, you can [convert it to an AWS Marketplace subscription](marketplace-trial-conversion.md) instead of creating a new account. + Some differences exist when you subscribe to {{ecloud}} through the AWS Marketplace: * Billing starts automatically after the 7-day trial period. -* Previous {{ecloud}} accounts cannot be converted to use the AWS Marketplace. If you already have an account, you must use a different email address when you sign up for a subscription through the AWS Marketplace. * Pricing is based on the AWS region, the size of your deployment, as well as some other parameters such as data transfer out, data transfer internode, snapshot storage, and snapshot APIs. For more details, check [Billing Dimensions](../../cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md). * The consolidated charges for your {{ecloud}} subscription display in the AWS Marketplace billing console. It can take a day or two before new charges show up. * Regardless of where your deployment is hosted (visible in the {{ecloud}} console), the AWS Marketplace charges for all AWS regions are metered in US East (Northern Virginia). As a result, US East (Northern Virginia) is listed as the region in the AWS Marketplace console. diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md index a0e5bcc813..7f2b4a3da5 100644 --- a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md @@ -193,7 +193,7 @@ $$$azure-integration-prior-cloud-account$$$I already have an {{ecloud}} account, : Yes. If you already have an {{ecloud}} account with the same email address as your Azure account you may need to contact `support@elastic.co`. $$$azure-integration-convert-trial$$$Can I sign up for an {{ecloud}} trial account and then convert to the {{ecloud}} Azure Native ISV Service? -: Yes. You can start a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body) and then convert your account over to Azure. There are a few requirements: +: Yes. You can start a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body) and then convert your account over to Azure. For step-by-step instructions, refer to [Convert a trial to a marketplace subscription](marketplace-trial-conversion.md). Keep in mind the following requirements: * Make sure when creating deployments in the trial account you specify Azure as the cloud provider. * To convert your trial to the Azure marketplace you need to create a deployment in the Azure console. Just delete the new deployment if you don’t need it. After you create the new deployment your marketplace subscription is ready. diff --git a/deploy-manage/deploy/elastic-cloud/create-an-organization.md b/deploy-manage/deploy/elastic-cloud/create-an-organization.md index 3cedbeafa9..ffea87f743 100644 --- a/deploy-manage/deploy/elastic-cloud/create-an-organization.md +++ b/deploy-manage/deploy/elastic-cloud/create-an-organization.md @@ -66,7 +66,7 @@ Subscribe to [{{ecloud}}](/deploy-manage/cloud-organization/billing/add-billing- * Third availability zone for your deployments. * Access to additional features, such as {{ccs}} and {{ccr}}. -You can subscribe to {{ecloud}} at any time during your trial. +You can subscribe to {{ecloud}} at any time during your trial by [adding your billing details](/deploy-manage/cloud-organization/billing/add-billing-details.md) or by [converting your trial to a marketplace subscription](marketplace-trial-conversion.md). [Billing](/deploy-manage/cloud-organization/billing/serverless-project-billing-dimensions.md) starts when you subscribe. To maximize the benefits of your trial, subscribe at the end of the free period. To monitor charges, anticipate future costs, and adjust your usage, check your [account usage](/deploy-manage/cloud-organization/billing/monitor-analyze-usage.md) and [billing history](/deploy-manage/cloud-organization/billing/view-billing-history.md). diff --git a/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md b/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md index 9db0299bbc..f456ba5014 100644 --- a/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md @@ -14,6 +14,8 @@ products: Subscribe to {{ecloud}} directly from the Google Cloud Platform (GCP). You then have the convenience of viewing your {{ecloud}} subscription as part of your GCP bill, and you do not have to supply any additional credit card information to Elastic. Your investment in Elastic draws against your cloud purchase commitment. +If you already have an {{ecloud}} trial, you can [convert it to a GCP Marketplace subscription](marketplace-trial-conversion.md) instead of creating a new organization through the GCP Marketplace. + Some differences exist when you subscribe to {{ecloud}} through the GCP Marketplace: * New {{ecloud}} customers obtain a 7-day trial period. During this period, you can use a single deployment and three projects of {{ecloud}}. After this period, usage-based billing starts, unless you delete your cloud resources. Note that once customers unsubscribe from the GCP offer, their trial will end immediately. Even if they resubscribe, they will not be able to resume the trial. diff --git a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md new file mode 100644 index 0000000000..99122068c1 --- /dev/null +++ b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md @@ -0,0 +1,75 @@ +--- +applies_to: + deployment: + ess: ga + serverless: ga +products: + - id: cloud-hosted + - id: cloud-serverless +--- + +# Convert a trial to a marketplace subscription [ec-marketplace-trial-conversion] + +If you started with an {{ecloud}} trial and want to pay through a cloud marketplace instead of adding a credit card directly, you can convert your trial to a marketplace subscription. Your existing deployments, projects, and data are preserved during the conversion. + +## Before you begin + +- You must have an active {{ecloud}} trial. If your trial has expired, you have 30 days to subscribe before your data is permanently deleted. +- You need access to one of the supported marketplaces: [{{aws}} Marketplace](aws-marketplace.md), [Azure Marketplace](azure-native-isv-service.md), or [{{gcp}} Marketplace](google-cloud-platform-marketplace.md). +- The email address associated with your {{ecloud}} trial must match the credentials you use during the marketplace sign-up process. + +## Convert your trial [ec-marketplace-trial-conversion-steps] + +% TODO: confirm exact UI labels per marketplace from Figma designs + +::::::{stepper} +:::::{step} Create your {{ecloud}} trial +If you haven't already, [sign up](create-an-organization.md) for an {{ecloud}} trial using the email address you prefer. This is the email address that will be associated with your marketplace subscription. +::::: +:::::{step} Subscribe through your marketplace +Log into your cloud provider's marketplace and find the {{ecloud}} offering. Select **Sign up** (or the equivalent action for your marketplace). + +::::{tab-set} +:::{tab-item} {{aws}} Marketplace +Go to the [{{ecloud}} listing on the {{aws}} Marketplace](https://aws.amazon.com/marketplace/pp/prodview-voru33wi6xs7k) and click **View purchase options**, then **Subscribe** and **Set Up Your Account**. +::: +:::{tab-item} Azure Marketplace +Go to the [{{ecloud}} ({{es}}) - An Azure Native ISV Service](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.ec-azure-pp) listing in the Azure portal. Select **Subscribe** and follow the prompts to create an Elastic resource. +::: +:::{tab-item} {{gcp}} Marketplace +Go to the [{{ecloud}} listing on the {{gcp}} Marketplace](https://console.cloud.google.com/marketplace/product/elastic-prod/elastic-cloud). Select **Subscribe**, accept the terms, and choose **Sign up with Elastic**. +::: +:::: +::::: +:::::{step} Sign in with your existing credentials +When prompted to create a new account or sign in, choose to **sign in** with the {{ecloud}} credentials from your existing trial. +::::: +:::::{step} Select the organization to convert +What happens next depends on how many organizations your account belongs to: + +- **Single organization:** Your trial organization is automatically converted to the marketplace subscription. Billing through the marketplace begins immediately. +- **Multiple organizations:** You are prompted to select which organization you want to convert to the marketplace subscription. Only eligible organizations are shown. + +% TODO: confirm auto-convert behavior for single org and add detail on the selection UI from Figma +::::: +:::::: + +## Which organizations can be converted [ec-marketplace-conversion-candidates] + +% TODO: confirm full eligibility criteria with PM/engineering + +Not all organizations are eligible for marketplace conversion. An organization can be converted if it meets the following conditions: + +- The organization is on a **trial** subscription (not already linked to another billing source). +- The organization does not already have a credit card or another marketplace subscription attached. + +If you belong to multiple organizations and none are eligible for conversion, you may need to create a new organization through the marketplace sign-up flow instead. + +## After conversion [ec-marketplace-post-conversion] + +After your trial is converted: + +- All existing deployments and projects in the converted organization are preserved. +- Billing starts through the marketplace immediately. There is no additional trial period. +- Your subscription level may change depending on the marketplace. Check your marketplace-specific page for details: [{{aws}}](aws-marketplace.md), [Azure](azure-native-isv-service.md), [{{gcp}}](google-cloud-platform-marketplace.md). +- To monitor your usage and costs, go to **Billing > Usage** in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). diff --git a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md index 06633da308..f1db2728e1 100644 --- a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md @@ -7,27 +7,29 @@ applies_to: serverless: ga products: - id: cloud-hosted + - id: cloud-serverless --- # Subscribe from a marketplace [ec-marketplaces] -% updates todo - -You can subscribe to {{ecloud}} from a marketplace. Your subscription gets billed together with other services that you’re already using, and can contribute towards your spend commitment with cloud providers. +You can subscribe to {{ecloud}} from a marketplace. Your subscription gets billed together with other services that you're already using, and can contribute towards your spend commitment with cloud providers. Trial availability and duration can vary depending on the marketplace. -When subscribing from a marketplace, your marketplace email is used for your [Elastic account](../../../cloud-account/update-your-email-address.md). - -* [AWS Marketplace](aws-marketplace.md) -* [Azure Marketplace](azure-native-isv-service.md) -* [GCP Marketplace](google-cloud-platform-marketplace.md) -* [Heroku](heroku.md) +## How marketplaces, organizations, and accounts work together [ec-marketplace-org-relationship] -::::{note} -[Serverless projects](https://docs.elastic.co/serverless) are only available for the AWS Marketplace, and are in technical preview on the Azure Marketplace. Support for GCP Marketplace will be added in the near future. -:::: +When you subscribe to {{ecloud}} through a marketplace, a relationship is established between your marketplace account and an {{ecloud}} [organization](/deploy-manage/cloud-organization.md). +- **One marketplace subscription maps to one {{ecloud}} organization.** Billing for all deployments and projects within that organization flows through the linked marketplace subscription. +- **Each organization can only be linked to a single billing source**: either a marketplace subscription or direct credit card billing. +- **A single {{ecloud}} account can belong to [multiple organizations](/deploy-manage/cloud-organization/manage-multiple-organizations.md).** When you subscribe through a marketplace, you can either create a new organization or link the subscription to an existing one. If your account has multiple organizations, you choose which organization to associate with the marketplace subscription. +- **Your {{ecloud}} account uses a single email address across all your organizations.** If you already have an {{ecloud}} account, you can sign in with your existing credentials during the marketplace sign-up process. If you don't have an account, one is created using your marketplace email. +If you already have an {{ecloud}} trial and want to start paying through a marketplace, you can [convert your trial to a marketplace subscription](marketplace-trial-conversion.md) without losing your existing deployments, projects, or data. +## Marketplace options +* [AWS Marketplace](aws-marketplace.md) +* [Azure Marketplace](azure-native-isv-service.md) +* [GCP Marketplace](google-cloud-platform-marketplace.md) +* [Heroku](heroku.md) ({{ech}} only - no organization functionality) diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 592abe369d..ffdda3ec33 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -11,6 +11,7 @@ toc: children: - file: deploy/elastic-cloud/subscribe-from-marketplace.md children: + - file: deploy/elastic-cloud/marketplace-trial-conversion.md - hidden: deploy/elastic-cloud/create-monthly-pay-as-you-go-subscription-on-aws-marketplace.md - hidden: deploy/elastic-cloud/complete-registration-of-an-annual-subscription-on-aws-marketplace.md - hidden: deploy/elastic-cloud/azure-marketplace-pricing.md From 5c97b942520e691a8c25ad1579b9d8a9d2032011 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 8 Apr 2026 14:50:00 -0400 Subject: [PATCH 11/19] marketplace edits --- .../deploy/elastic-cloud/aws-marketplace.md | 4 +- .../google-cloud-platform-marketplace.md | 5 +- .../marketplace-trial-conversion.md | 65 ++++++++++++------- .../subscribe-from-marketplace.md | 19 +++--- 4 files changed, 57 insertions(+), 36 deletions(-) diff --git a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md index f46ac91814..6d078d18a9 100644 --- a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md @@ -44,7 +44,6 @@ Elastic provides different [subscription levels](https://www.elastic.co/subscrip Note the following items before you subscribe: -* You cannot use an email address that already has an {{ecloud}} account. If you want to use the same account email address with AWS Marketplace billing, you must first change the email address on your existing account before setting up your new AWS Marketplace subscription. For instructions on how to change your email address in {{ecloud}}, check [update your email address](../../../cloud-account/update-your-email-address.md). * If you want to manage deployments on the existing {{ecloud}} account with your AWS MP billing account, you must migrate your deployments over to the new MP billing account. To migrate, use a [custom repository](../../tools/snapshot-and-restore/elastic-cloud-hosted.md) to take a snapshot and then restore that snapshot to a new deployment under your AWS Marketplace account. @@ -57,7 +56,7 @@ To subscribe to {{ecloud}} through the AWS Marketplace: 3. Follow the steps displayed to complete the signup process. 1. Ensure that you have the necessary AWS permissions required to complete a marketplace transaction. - 2. Create a new {{ecloud}} account. This account is linked to your AWS Marketplace subscription. + 2. Create a new {{ecloud}} account or log in with an existing account. This account is linked to your AWS Marketplace subscription. 3. (Optional) Use the {{ecloud}} CloudFormation template to quickly get started with Elastic. The template deploys the {{stack}} in your {{ecloud}} account, and also provisions the {{agent}} on a new EC2 instance in your AWS environment. 4. Navigate to {{ecloud}} to continue. @@ -91,6 +90,7 @@ If the {{ecloud}} login page displays when coming from the AWS console, then an If you can’t remember which email address you used to sign up to {{ecloud}}, or you need more help, contact `support@elastic.co`. +% is this still true? ### When I try to configure an account from the AWS console I get an error that an active AWS subscription already exists. [ec-awsmp-account-collision03] This error occurs when you have already provisioned a marketplace subscription under your AWS user account. Each AWS user account can only subscribe to {{ecloud}} once. diff --git a/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md b/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md index f456ba5014..d4be94bc33 100644 --- a/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md @@ -22,6 +22,7 @@ Some differences exist when you subscribe to {{ecloud}} through the GCP Marketpl * Pricing for an {{ecloud}} subscription through the GCP Marketplace follows the pricing outlined on the [{{ecloud}}](https://console.cloud.google.com/marketplace/product/elastic-prod/elastic-cloud) page in the GCP Marketplace. Pricing is based the {{ecloud}} [billing dimensions](../../cloud-organization/billing.md#pricing-model). * To access your billing information at any time go to **Account & Billing**. You can also go to **Account & Billing** and then **Usage** to view your usage hours and units per hour. +% is this still true? ::::{important} Only one {{ecloud}} organization can be subscribed through GCP Marketplace per GCP billing account. :::: @@ -36,8 +37,8 @@ To subscribe to {{ecloud}} through the GCP Marketplace: 5. When you are presented with a pop-up that specifies that "Your order request has been sent to Elastic" choose **Sign up with Elastic** to continue. 6. After choosing to sign up, a new window will appear. Do one of the following: - * Create a new, unique user account for an {{ecloud}} {{ecloud}} organization. - * Log in with an existing user account that’s associated with an {{ecloud}} trial. This links the billing account used for the purchase on GCP Marketplace to the existing Elastic organization. + * Create a new, unique user account for an {{ecloud}} organization. + * Log in with an existing user account. If the account is associated with an {{ecloud}} trial, it links the billing account used for the purchase on GCP Marketplace to the existing Elastic organization. [Learn more](marketplace-trial-conversion.md). 7. After signing up, check your inbox to verify the email address you signed up with. Upon verification, you will be asked to create a password, and once created your organization will be set up and you will be logged into it. diff --git a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md index 99122068c1..d8626f6ca6 100644 --- a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md +++ b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md @@ -5,65 +5,84 @@ applies_to: serverless: ga products: - id: cloud-hosted - - id: cloud-serverless --- # Convert a trial to a marketplace subscription [ec-marketplace-trial-conversion] -If you started with an {{ecloud}} trial and want to pay through a cloud marketplace instead of adding a credit card directly, you can convert your trial to a marketplace subscription. Your existing deployments, projects, and data are preserved during the conversion. +If you started with an {{ecloud}} trial and want to pay through a cloud marketplace instead of adding a credit card directly, you can convert your trial organization to a marketplace subscription. Your existing deployments, projects, and data are preserved during the conversion. -## Before you begin +This works for both active and expired trials, as long as the organization is eligible for conversion and the data retention window has not passed. -- You must have an active {{ecloud}} trial. If your trial has expired, you have 30 days to subscribe before your data is permanently deleted. -- You need access to one of the supported marketplaces: [{{aws}} Marketplace](aws-marketplace.md), [Azure Marketplace](azure-native-isv-service.md), or [{{gcp}} Marketplace](google-cloud-platform-marketplace.md). -- The email address associated with your {{ecloud}} trial must match the credentials you use during the marketplace sign-up process. +## Requirements -## Convert your trial [ec-marketplace-trial-conversion-steps] +- An {{ecloud}} trial organization that is [eligible for conversion](#ec-marketplace-conversion-candidates). +- Access to one of the supported marketplaces: [{{aws}} Marketplace](aws-marketplace.md), [Azure Marketplace](azure-native-isv-service.md), or [{{gcp}} Marketplace](google-cloud-platform-marketplace.md). +- The email address associated with your {{ecloud}} account matches the credentials you use during the marketplace sign-up process. +- To convert from the Azure Marketplace: your {{ecloud}} account must only be owner of a single [convertible](#ec-marketplace-conversion-candidates) organization. -% TODO: confirm exact UI labels per marketplace from Figma designs +## Convert your trial in {{aws}} and {{gcp}} marketplaces [ec-marketplace-trial-conversion-aws-gcp] + +For {{aws}} and {{gcp}}, you complete the subscription in the marketplace and then sign in to {{ecloud}} to link the subscription to an organization. ::::::{stepper} :::::{step} Create your {{ecloud}} trial -If you haven't already, [sign up](create-an-organization.md) for an {{ecloud}} trial using the email address you prefer. This is the email address that will be associated with your marketplace subscription. +If you haven't already, [sign up](create-an-organization.md) for an {{ecloud}} trial using the email address you prefer. ::::: :::::{step} Subscribe through your marketplace -Log into your cloud provider's marketplace and find the {{ecloud}} offering. Select **Sign up** (or the equivalent action for your marketplace). ::::{tab-set} :::{tab-item} {{aws}} Marketplace Go to the [{{ecloud}} listing on the {{aws}} Marketplace](https://aws.amazon.com/marketplace/pp/prodview-voru33wi6xs7k) and click **View purchase options**, then **Subscribe** and **Set Up Your Account**. ::: -:::{tab-item} Azure Marketplace -Go to the [{{ecloud}} ({{es}}) - An Azure Native ISV Service](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.ec-azure-pp) listing in the Azure portal. Select **Subscribe** and follow the prompts to create an Elastic resource. -::: :::{tab-item} {{gcp}} Marketplace Go to the [{{ecloud}} listing on the {{gcp}} Marketplace](https://console.cloud.google.com/marketplace/product/elastic-prod/elastic-cloud). Select **Subscribe**, accept the terms, and choose **Sign up with Elastic**. ::: :::: ::::: :::::{step} Sign in with your existing credentials -When prompted to create a new account or sign in, choose to **sign in** with the {{ecloud}} credentials from your existing trial. +When prompted to create a new account or sign in, choose to **sign in** with your existing {{ecloud}} credentials. ::::: :::::{step} Select the organization to convert What happens next depends on how many organizations your account belongs to: -- **Single organization:** Your trial organization is automatically converted to the marketplace subscription. Billing through the marketplace begins immediately. -- **Multiple organizations:** You are prompted to select which organization you want to convert to the marketplace subscription. Only eligible organizations are shown. +- **Single convertible trial organization:** You are presented with an option to convert the trial to the marketplace subscription. Billing through the marketplace begins immediately upon conversion. +- **Multiple organizations:** You are shown a list of your organizations. Organizations that are eligible for conversion have a **Convert** option. Select the organization you want to convert. + +You can also choose to **create a new organization** instead of converting an existing one. The new organization starts with its own 7-day marketplace trial. + +% TODO: confirm CTA labels from Figma -% TODO: confirm auto-convert behavior for single org and add detail on the selection UI from Figma +If none of your existing organizations are eligible for conversion, you can still create a new organization through the marketplace, or refer to [Which organizations can be converted](#ec-marketplace-conversion-candidates) to understand why. ::::: :::::: -## Which organizations can be converted [ec-marketplace-conversion-candidates] +## Convert your trial in the Azure Marketplace [ec-marketplace-trial-conversion-azure] -% TODO: confirm full eligibility criteria with PM/engineering +The Azure flow works differently because Elastic resources are created directly from the Azure portal. + +::::::{stepper} +:::::{step} Create your {{ecloud}} trial +If you haven't already, [sign up](create-an-organization.md) for an {{ecloud}} trial using the email address you prefer. +::::: +:::::{step} Create an Elastic resource from the Azure portal +Go to the [{{ecloud}} ({{es}}) - An Azure Native ISV Service](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.ec-azure-pp) listing in the Azure portal. Select **Subscribe** and follow the prompts to create an Elastic resource. + +When you create the resource, it is automatically linked to your existing trial organization if you have a single eligible trial. You can delete the new deployment afterward if you don't need it. +::::: +:::::: + +::::{note} +If your account has multiple trial organizations that are eligible for conversion, you cannot convert from the Azure portal. You must leave the other trial organizations first so that only one eligible organization remains. For more details, refer to [Azure Native ISV Service](azure-native-isv-service.md). +:::: + +## Which organizations can be converted [ec-marketplace-conversion-candidates] Not all organizations are eligible for marketplace conversion. An organization can be converted if it meets the following conditions: -- The organization is on a **trial** subscription (not already linked to another billing source). +- The {{ecloud}} account that you log in with is the owner of the organization. +- The organization is on a **trial** subscription (active or expired). - The organization does not already have a credit card or another marketplace subscription attached. - -If you belong to multiple organizations and none are eligible for conversion, you may need to create a new organization through the marketplace sign-up flow instead. +- The organization's deployments and projects are hosted on the same cloud provider as the marketplace. For example, an organization with deployments on {{aws}} can only be converted to an {{aws}} Marketplace subscription, not a {{gcp}} Marketplace subscription. ## After conversion [ec-marketplace-post-conversion] @@ -71,5 +90,5 @@ After your trial is converted: - All existing deployments and projects in the converted organization are preserved. - Billing starts through the marketplace immediately. There is no additional trial period. -- Your subscription level may change depending on the marketplace. Check your marketplace-specific page for details: [{{aws}}](aws-marketplace.md), [Azure](azure-native-isv-service.md), [{{gcp}}](google-cloud-platform-marketplace.md). +- Your subscription level might change depending on the marketplace. Check your marketplace-specific page for details: [{{aws}}](aws-marketplace.md), [Azure](azure-native-isv-service.md), [{{gcp}}](google-cloud-platform-marketplace.md). - To monitor your usage and costs, go to **Billing > Usage** in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). diff --git a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md index f1db2728e1..7591232ad8 100644 --- a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md @@ -16,20 +16,21 @@ You can subscribe to {{ecloud}} from a marketplace. Your subscription gets bille Trial availability and duration can vary depending on the marketplace. +## Marketplace options + +* [AWS Marketplace](aws-marketplace.md) +* [Azure Marketplace](azure-native-isv-service.md) +* [GCP Marketplace](google-cloud-platform-marketplace.md) +* [Heroku](heroku.md) ({{ech}} only - no organization functionality) + + ## How marketplaces, organizations, and accounts work together [ec-marketplace-org-relationship] When you subscribe to {{ecloud}} through a marketplace, a relationship is established between your marketplace account and an {{ecloud}} [organization](/deploy-manage/cloud-organization.md). - **One marketplace subscription maps to one {{ecloud}} organization.** Billing for all deployments and projects within that organization flows through the linked marketplace subscription. - **Each organization can only be linked to a single billing source**: either a marketplace subscription or direct credit card billing. -- **A single {{ecloud}} account can belong to [multiple organizations](/deploy-manage/cloud-organization/manage-multiple-organizations.md).** When you subscribe through a marketplace, you can either create a new organization or link the subscription to an existing one. If your account has multiple organizations, you choose which organization to associate with the marketplace subscription. +- **A single {{ecloud}} account can belong to [multiple organizations](/deploy-manage/cloud-organization/manage-multiple-organizations.md).** When you subscribe through a marketplace, you can either create a new organization or link the subscription to an existing one. If your account is organization owner for multiple organizations, you choose which organization to associate with the marketplace subscription. - **Your {{ecloud}} account uses a single email address across all your organizations.** If you already have an {{ecloud}} account, you can sign in with your existing credentials during the marketplace sign-up process. If you don't have an account, one is created using your marketplace email. -If you already have an {{ecloud}} trial and want to start paying through a marketplace, you can [convert your trial to a marketplace subscription](marketplace-trial-conversion.md) without losing your existing deployments, projects, or data. - -## Marketplace options - -* [AWS Marketplace](aws-marketplace.md) -* [Azure Marketplace](azure-native-isv-service.md) -* [GCP Marketplace](google-cloud-platform-marketplace.md) -* [Heroku](heroku.md) ({{ech}} only - no organization functionality) +If you already have an {{ecloud}} trial and want to start paying through a marketplace, you can [convert your trial to a marketplace subscription](marketplace-trial-conversion.md) without losing your existing deployments, projects, or data. \ No newline at end of file From 62ed742a4dbc702843723fc084e6778a0eb68a2f Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 8 Apr 2026 15:46:05 -0400 Subject: [PATCH 12/19] marketplaces cont'd --- .../deploy/elastic-cloud/aws-marketplace.md | 5 ++-- .../elastic-cloud/azure-native-isv-service.md | 30 ++++++++++++------- .../marketplace-trial-conversion.md | 17 +++++------ .../subscribe-from-marketplace.md | 27 +++++++++++++---- 4 files changed, 50 insertions(+), 29 deletions(-) diff --git a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md index 6d078d18a9..970e09a3d8 100644 --- a/deploy-manage/deploy/elastic-cloud/aws-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/aws-marketplace.md @@ -44,7 +44,8 @@ Elastic provides different [subscription levels](https://www.elastic.co/subscrip Note the following items before you subscribe: -* If you want to manage deployments on the existing {{ecloud}} account with your AWS MP billing account, you must migrate your deployments over to the new MP billing account. To migrate, use a [custom repository](../../tools/snapshot-and-restore/elastic-cloud-hosted.md) to take a snapshot and then restore that snapshot to a new deployment under your AWS Marketplace account. +* Each AWS billing account supports one {{ecloud}} subscription, which maps to one {{ecloud}} organization. If you need multiple organizations (for example, separate production and development environments), use separate AWS accounts. +* If you want to migrate deployments from an existing non-marketplace organization into your AWS Marketplace organization, use a [custom repository](../../tools/snapshot-and-restore/elastic-cloud-hosted.md) to take a snapshot and then restore it to a new deployment under your AWS Marketplace organization. ## Subscribe to {{ecloud}} through the AWS Marketplace [ec_subscribe_to_elasticsearch_service_through_the_aws_marketplace] @@ -79,7 +80,7 @@ This section describes some scenarios that you may experience onboarding onto th This occurs when you attempt to sign up to the marketplace offer using an email address that already exists in {{ecloud}}, such as part of a trial account. You have a few options: -* **Change the email address of your previous {{ecloud}} account** - Log in to your existing {{ecloud}} account and change the email address. Once changed, navigate back to the AWS console to finish setting up your marketplace subscription. +* **Sign in with your existing account** - Choose to sign in instead of signing up. You can then [convert an existing trial organization](marketplace-trial-conversion.md) to your AWS Marketplace subscription or create a new organization. * **Sign up using a different email address** - Sign up to {{ecloud}} using a different email address. diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md index 548f57cbfc..eae8daf58c 100644 --- a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md @@ -41,7 +41,7 @@ $$$ec-supported-regions$$$ Before setting up an {{ecloud}} deployment or project through the Azure Native ISV Service, review the following requirements: * Your Azure account role for the subscription must be set to **Owner** or **Contributor**. For details and steps to assign roles, refer to [Roles and permissions](https://learn.microsoft.com/en-us/marketplace/roles-permissions#roles-and-permissions-1) in the Azure documentation. -* You can't use an email address that already has an {{ecloud}} account. Use a different Azure account to set up the {{es}} resource, or [contact Elastic Support](azure-native-isv-service-troubleshooting.md#azure-integration-support) for assistance. For a workaround, refer to [Sign up using an existing email address](//cloud-account/update-your-email-address.md#sign-up-existing). +* If you already have an {{ecloud}} account, you can sign in with your existing credentials during setup. Your new resource will be linked to an existing organization or a new one will be created. For details on how accounts and organizations work together, refer to [Subscribe from a marketplace](subscribe-from-marketplace.md#ec-marketplace-org-relationship). * You must have a credit card registered on your Azure subscription. If you have a non-payment subscription, such as a [Virtual Studio Subscription](https://visualstudio.microsoft.com/subscriptions/), you can't create an {{ecloud}} deployment. Refer to the Azure [Purchase errors](https://learn.microsoft.com/en-us/azure/partner-solutions/elastic/troubleshoot#marketplace-purchase-errors) troubleshooting documentation for more information. * To single sign-on into your {{ecloud}} deployment or project from Azure, you need to request approval from your Azure administrator. @@ -100,25 +100,34 @@ You have a few options to access your deployment or project: * [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md#ec_how_to_operate_elasticsearch_service) * [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md#get-started) +## Multi-org accounts and the Azure portal [ec-azure-multi-org-limitations] + +Unlike {{aws}} and {{gcp}}, the Azure portal does not provide an organization picker during resource creation. When your account has a single organization, the Azure portal automatically adds new resources to that organization and can handle trial conversion. When your account has multiple organizations, the portal may not be able to determine which organization to target. + +The following limitations apply: + +- **Multiple Azure MP organizations:** You can't create resources from the Azure portal. Create resources directly from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) instead, where you can select the specific organization to use. +- **Multiple eligible trial organizations:** You can't convert a trial from the Azure portal. To resolve this, leave the other trial organizations so that only one eligible organization remains. Alternatively, use the [{{aws}}](aws-marketplace.md) or [{{gcp}}](google-cloud-platform-marketplace.md) marketplace instead, which support an organization picker during sign-up. + ## Trials and existing accounts [ec-azure-integration-trials] -% needs to be updated for multi org $$$azure-integration-prior-cloud-account$$$ -If you already have an {{ecloud}} account with the same email address as your Azure account, you might need to contact `support@elastic.co`. +If you already have an {{ecloud}} account, you can sign in with your existing credentials when creating an Elastic resource in the Azure portal. If your account has a single organization, the resource is added to that organization. If you have multiple organizations, refer to [Multi-org accounts and the Azure portal](#ec-azure-multi-org-limitations). ### Convert a trial to Azure ISV [azure-integration-convert-trial] -You can start a [free {{ecloud}} trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body) and then convert your organization over to Azure. There are a few requirements: +If you have an existing {{ecloud}} trial, you can convert it to an Azure Marketplace subscription. For step-by-step instructions, refer to [Convert a trial to a marketplace subscription](marketplace-trial-conversion.md#ec-marketplace-trial-conversion-azure). + +Keep in mind: -* Make sure when creating resources in the trial account that you specify Azure as the cloud provider. -* To convert your trial to the Azure marketplace you need to [create a resource](/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md#ec-azure-integration-getting-started) in the Azure console. Delete this resource if you don't need it. After you create the new resource, your marketplace subscription is ready. +* When creating resources in the trial account, specify Azure as the cloud provider so that the organization is [eligible for conversion](marketplace-trial-conversion.md#ec-marketplace-conversion-candidates). +* To convert your trial to the Azure Marketplace, [create a resource](#ec-azure-integration-getting-started) in the Azure console. Delete this resource if you don't need it. After you create the new resource, your marketplace subscription is ready. * Any resources created during your trial won't show up in the Azure console, because they weren't created in Azure, but they are still accessible through the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and you are billed for their usage. ### Start a trial from Azure Marketplace [azure-integration-native-trials] You can start a 7-day trial by creating a deployment through the Azure Marketplace. The following restrictions apply: -* The email associated with the Azure account used to create the deployment must not already be linked to an existing Elastic organization. * During the 7-day trial period, you can create up to one deployment and three serverless projects. If you want to convert to a paid subscription before the end of the trial period, contact `support@elastic.co`. * After 7 days, the trial will automatically convert to a paid offering. You can contact Elastic Support to unsubscribe, but doing so might result in your resources being deleted after a grace period. * You can sign up for only one trial per user account. After the trial expires, you can't start another trial. If you need a trial extension, reach out to Elastic Support. @@ -155,7 +164,7 @@ The integrated billing process involves the following concepts: The following diagram shows the mapping between Microsoft Azure IDs, {{ecloud}} organization IDs, and your Elastic resources (deployments). -% needs to be updated for multi org +% TODO: update diagram for multi-org :::{image} /deploy-manage/images/cloud-ec-azure-billing-mapping.png :alt: Azure to {{ecloud}} mappings ::: @@ -189,9 +198,8 @@ $$$azure-integration-billing-which-subscription$$$ The Azure Marketplace integrated billing posts all of the Elastic resource costs related to an {{ecloud}} organization to the Azure subscription you used to create your first-ever Elastic resource, even if your individual Elastic resources (deployments and projects) are spread across different Azure subscriptions. -% needs to be updated for multi org $$$azure-integration-billing-different-deployments$$$ -To have different Elastic resources' costs reported to different Azure subscriptions, they need to be in separate {{ecloud}} organizations. To create a separate {{ecloud}} organization from an Azure subscription, you will need to subscribe as a user who is not already part of an existing {{ecloud}} organization. +To have different Elastic resources' costs reported to different Azure subscriptions, they need to be in separate {{ecloud}} organizations. To create a separate organization, [create a new Elastic resource](#ec-azure-integration-getting-started) from the Azure portal. A new organization is created as part of the resource creation process. #### How costs are reported @@ -226,7 +234,7 @@ There are several options to integrate Microsoft authentication with {{ecloud}}: * [{{ecloud}} RBAC capabilities](../../users-roles/cloud-organization/user-roles.md) are available only from the {{ecloud}} Console and is not integrated with Azure Portal. Users who interact with Elastic resources from Azure Portal will not be recognized by the {{ecloud}} RBAC policies. $$$azure-integration-authorization-access$$$ -* Elastic is not currently integrated with Azure user management. Azure users who deploy {{es}} 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. +* Elastic is not currently integrated with Azure user management. Azure users who deploy {{es}} on Azure view and manage their own cluster through the Cloud console. Other Azure users in the same tenant can't access clusters through the Cloud console other than those that they themselves created. When trying to access resources such as {{es}}, {{kib}}, or {{product.apm}} in a deployment or project that was created by another Azure user, the following error is shown: diff --git a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md index d8626f6ca6..67215d1b31 100644 --- a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md +++ b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md @@ -58,37 +58,34 @@ If none of your existing organizations are eligible for conversion, you can stil ## Convert your trial in the Azure Marketplace [ec-marketplace-trial-conversion-azure] -The Azure flow works differently because Elastic resources are created directly from the Azure portal. +The Azure flow works differently from {{aws}} and {{gcp}} because Elastic resources are created directly from the Azure portal rather than through an Elastic sign-up page. ::::::{stepper} :::::{step} Create your {{ecloud}} trial -If you haven't already, [sign up](create-an-organization.md) for an {{ecloud}} trial using the email address you prefer. +If you haven't already, [sign up](create-an-organization.md) for an {{ecloud}} trial using the email address you prefer. When creating resources during the trial, specify Azure as the cloud provider so that the organization is [eligible for conversion](#ec-marketplace-conversion-candidates). ::::: :::::{step} Create an Elastic resource from the Azure portal Go to the [{{ecloud}} ({{es}}) - An Azure Native ISV Service](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.ec-azure-pp) listing in the Azure portal. Select **Subscribe** and follow the prompts to create an Elastic resource. -When you create the resource, it is automatically linked to your existing trial organization if you have a single eligible trial. You can delete the new deployment afterward if you don't need it. +When you create the resource, it is linked to your existing trial organization and the trial is converted to an Azure Marketplace subscription. You can delete the new deployment afterward if you don't need it. ::::: :::::: -::::{note} -If your account has multiple trial organizations that are eligible for conversion, you cannot convert from the Azure portal. You must leave the other trial organizations first so that only one eligible organization remains. For more details, refer to [Azure Native ISV Service](azure-native-isv-service.md). -:::: - ## Which organizations can be converted [ec-marketplace-conversion-candidates] Not all organizations are eligible for marketplace conversion. An organization can be converted if it meets the following conditions: -- The {{ecloud}} account that you log in with is the owner of the organization. -- The organization is on a **trial** subscription (active or expired). +- You are the owner of the organization. +- The organization is on a trial subscription (active or expired). - The organization does not already have a credit card or another marketplace subscription attached. - The organization's deployments and projects are hosted on the same cloud provider as the marketplace. For example, an organization with deployments on {{aws}} can only be converted to an {{aws}} Marketplace subscription, not a {{gcp}} Marketplace subscription. +If none of your organizations are eligible, you can create a new organization through the marketplace sign-up flow, or [subscribe directly](/deploy-manage/cloud-organization/billing/add-billing-details.md) with a credit card. + ## After conversion [ec-marketplace-post-conversion] After your trial is converted: - All existing deployments and projects in the converted organization are preserved. - Billing starts through the marketplace immediately. There is no additional trial period. -- Your subscription level might change depending on the marketplace. Check your marketplace-specific page for details: [{{aws}}](aws-marketplace.md), [Azure](azure-native-isv-service.md), [{{gcp}}](google-cloud-platform-marketplace.md). - To monitor your usage and costs, go to **Billing > Usage** in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). diff --git a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md index 7591232ad8..bcb3b8689c 100644 --- a/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md +++ b/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md @@ -12,25 +12,40 @@ products: # Subscribe from a marketplace [ec-marketplaces] -You can subscribe to {{ecloud}} from a marketplace. Your subscription gets billed together with other services that you're already using, and can contribute towards your spend commitment with cloud providers. +You can subscribe to {{ecloud}} from a cloud marketplace instead of paying Elastic directly. Marketplace subscriptions offer the following benefits: + +- **Consolidated billing.** Your {{ecloud}} charges appear on your existing cloud provider bill alongside your other services. +- **Spend commitment.** Your {{ecloud}} usage draws against your committed spend with your cloud provider. If you subscribe directly to Elastic (with a credit card or an Elastic contract), your {{ecloud}} spend does not count toward any cloud provider commitment. +- **Simplified procurement.** No need to set up a separate billing relationship with Elastic. Trial availability and duration can vary depending on the marketplace. ## Marketplace options -* [AWS Marketplace](aws-marketplace.md) +* [{{aws}} Marketplace](aws-marketplace.md) * [Azure Marketplace](azure-native-isv-service.md) -* [GCP Marketplace](google-cloud-platform-marketplace.md) +* [{{gcp}} Marketplace](google-cloud-platform-marketplace.md) * [Heroku](heroku.md) ({{ech}} only - no organization functionality) - ## How marketplaces, organizations, and accounts work together [ec-marketplace-org-relationship] When you subscribe to {{ecloud}} through a marketplace, a relationship is established between your marketplace account and an {{ecloud}} [organization](/deploy-manage/cloud-organization.md). -- **One marketplace subscription maps to one {{ecloud}} organization.** Billing for all deployments and projects within that organization flows through the linked marketplace subscription. +- **One marketplace subscription maps to one {{ecloud}} organization.** Billing for all deployments and projects within that organization flows through the linked marketplace subscription. The specifics vary by marketplace: + - **{{aws}}**: One subscription for each {{aws}} billing account. Customers with multiple {{aws}} accounts (for example, production and development) can have separate subscriptions, each linked to its own {{ecloud}} organization. + - **{{gcp}}**: One {{ecloud}} organization for each {{gcp}} billing account. + - **Azure**: Organization creation is tied to Elastic resource creation in the Azure portal, so customers who create multiple resources can accumulate multiple organizations. - **Each organization can only be linked to a single billing source**: either a marketplace subscription or direct credit card billing. - **A single {{ecloud}} account can belong to [multiple organizations](/deploy-manage/cloud-organization/manage-multiple-organizations.md).** When you subscribe through a marketplace, you can either create a new organization or link the subscription to an existing one. If your account is organization owner for multiple organizations, you choose which organization to associate with the marketplace subscription. - **Your {{ecloud}} account uses a single email address across all your organizations.** If you already have an {{ecloud}} account, you can sign in with your existing credentials during the marketplace sign-up process. If you don't have an account, one is created using your marketplace email. -If you already have an {{ecloud}} trial and want to start paying through a marketplace, you can [convert your trial to a marketplace subscription](marketplace-trial-conversion.md) without losing your existing deployments, projects, or data. \ No newline at end of file +If you already have an {{ecloud}} trial and want to start paying through a marketplace, you can [convert your trial to a marketplace subscription](marketplace-trial-conversion.md) without losing your existing deployments, projects, or data. + +## Multi-cloud strategy [ec-marketplace-multi-cloud] + +Because a single {{ecloud}} account can belong to multiple organizations, and each organization can be linked to a different marketplace, you can subscribe to multiple marketplaces to support a multi-cloud strategy. For example, you might have: + +- An {{aws}} Marketplace subscription for an organization running production workloads on {{aws}} +- A {{gcp}} Marketplace subscription for a separate organization running analytics workloads on {{gcp}} + +Each subscription draws against the respective cloud provider's spend commitment, letting you maximize the benefits of each marketplace independently. From ecdb17655af7c2c2fab3d5a8454b525db722fd7d Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 24 Jun 2026 15:54:05 -0400 Subject: [PATCH 13/19] changes from tech preview content --- .../join-or-leave-an-organization.md | 30 ++++++++++++++++--- cloud-account/switch-organizations.md | 11 +++++++ .../_snippets/switch-orgs.md | 12 +------- .../_snippets/invite-additional-orgs.md | 2 +- 4 files changed, 39 insertions(+), 16 deletions(-) diff --git a/cloud-account/join-or-leave-an-organization.md b/cloud-account/join-or-leave-an-organization.md index f5b9fe1896..b2327fb4ed 100644 --- a/cloud-account/join-or-leave-an-organization.md +++ b/cloud-account/join-or-leave-an-organization.md @@ -21,12 +21,34 @@ This guide explains how to join or leave an organization. To learn how to view o ## Accept an invitation [ec-accept-invitation] -Invitations to join an organization are sent by email. Invited users have 72 hours to accept the invitation. If they do not join within that period, an administrator of the organization will have to send a new invitation. Refer to [manage users](/deploy-manage/users-roles/cloud-organization/manage-users.md) for more information. +When you're invited to join an organization, you receive an email with a link to accept the invitation. Invitations expire after 72 hours. If you don't accept within that period, an administrator of the organization needs to send a new invitation. Refer to [manage users](/deploy-manage/users-roles/cloud-organization/manage-users.md) for more information. -If you're a member of more than one organization, then after you accept an invitation, the new organization appears in your list of organizations. You can switch to the new organization by clicking the organization name in the list. Refer to [Switch between organizations](/cloud-account/switch-organizations.md) for more information. +To accept an invitation: + +1. Open the invitation email and click **Accept invitation**. +2. Log in if prompted. If you already have an active session in your browser, you don't need to log in again. +3. After accepting, you're switched to the new organization automatically. The new organization also appears in your [list of organizations](/cloud-account/switch-organizations.md). + +:::{note} +If the organization enforces a specific login method, such as SAML SSO, you're redirected to that login flow when accepting the invitation. +::: + +To decline an invitation, you can ignore the email. The invitation expires automatically after 72 hours. ## Leave an organization [ec-leave-organization] -On the **Members** tab of the **Organization** page, click the three dots corresponding to your email address and select **Leave organization**. +You can leave an organization at any time, as long as you are a member of at least one other organization. If you are the only owner of an organization, you must transfer ownership before leaving. + +You can leave only the organization you're currently signed in to. To leave a different organization, [switch to it](/cloud-account/switch-organizations.md) first. + +:::{warning} +Leaving an organization revokes your access to all of its resources, including deployments, projects, and settings. This action cannot be undone. To rejoin the organization, ask an organization owner to invite you again. +::: + +To leave your current organization: -If you’re the only user in the organization, you can only leave if you deleted all your deployments and projects, and you don’t have pending bills. +1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). +2. From the top navigation menu, click on the user menu and select **Profile**. +3. Click the **My organizations** tab. +4. Click **Leave current organization**. +5. In the confirmation dialog, click **Leave current organization** to confirm. diff --git a/cloud-account/switch-organizations.md b/cloud-account/switch-organizations.md index 081bd55a63..5ad540a732 100644 --- a/cloud-account/switch-organizations.md +++ b/cloud-account/switch-organizations.md @@ -25,6 +25,17 @@ If you're an organization owner, then you can learn more about managing multiple To join an additional organization, [accept an invitation](/cloud-account/join-or-leave-an-organization.md#ec-accept-invitation) to join the organization. You can also [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). ::: +## Log in with multiple organizations + +When you belong to multiple organizations, the login experience depends on whether your browser has information about the organization you most recently used: + +* **Returning user (same browser):** You're automatically logged in to the organization you last used. You don't need to select an organization. +* **New browser or cleared data:** After logging in, you're presented with a list of your organizations to choose from. Select the organization you want to access. + +If your last used organization enforces a specific login method (such as SAML SSO), you're directed to that login flow automatically. + +If you log out, your browser remembers which organization you last used. The next time you log in, you're directed to the appropriate login page for that organization. + :::{include} /deploy-manage/cloud-organization/_snippets/view-orgs.md ::: diff --git a/deploy-manage/cloud-organization/_snippets/switch-orgs.md b/deploy-manage/cloud-organization/_snippets/switch-orgs.md index 1824d3a3d5..aea6b9684a 100644 --- a/deploy-manage/cloud-organization/_snippets/switch-orgs.md +++ b/deploy-manage/cloud-organization/_snippets/switch-orgs.md @@ -2,17 +2,7 @@ You can switch between organizations at any time. Depending on the authentication requirements for the organization, you might be required to re-authenticate. Switching also ends any active {{ecloud}} sessions you have open in other browser tabs. -### From your user profile - 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. From the top navigation menu, click on the user menu and select **Profile**. 3. Click the **My organizations** tab. -4. Click the name of the organization you want to switch to. If it doesn't appear in the list, click **Manage organizations** to view all of the organizations you have access to. - -### From the My organizations menu - -1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. From the top navigation menu, in the breadcrumb list, click the name of your current organization. -3. Click on the organization that you want to log into, or -4. Click the **My organizations** tab. -5. Click the name of the organization you want to switch to. \ No newline at end of file +4. Click the name of the organization you want to switch to. If it doesn't appear in the list, click **Manage organizations** to view all of the organizations you have access to. \ No newline at end of file diff --git a/deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md b/deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md index 0e97b531a1..203238f54a 100644 --- a/deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md +++ b/deploy-manage/users-roles/cloud-organization/_snippets/invite-additional-orgs.md @@ -1,4 +1,4 @@ -Because users are managed at the organization level, you must [invite users](/deploy-manage/users-roles/cloud-organization/manage-users.md#ec-invite-users) from within the organization that you want them to join. You can't invite users to join multiple organizations at once. +You must [send invitations](/deploy-manage/users-roles/cloud-organization/manage-users.md#ec-invite-users) from the organization you want users to join. You can't invite users to join multiple organizations at once. If a user already has an {{ecloud}} account, then they don't need to sign up again. Instead, they can log in with their selected login method. From 8afeaa1b923832c8575e90534f18f7ddcbe00b48 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 24 Jun 2026 16:04:06 -0400 Subject: [PATCH 14/19] xrefs --- cloud-account/index.md | 2 +- cloud-account/join-or-leave-an-organization.md | 8 ++++++-- cloud-account/switch-organizations.md | 18 +++++++++--------- .../manage-multiple-organizations.md | 4 ++++ 4 files changed, 20 insertions(+), 12 deletions(-) diff --git a/cloud-account/index.md b/cloud-account/index.md index 157e68bdc8..308d1e070c 100644 --- a/cloud-account/index.md +++ b/cloud-account/index.md @@ -45,7 +45,7 @@ If you use password-based login, then you can perform the following additional t Organizations are groupings of {{ecloud}} resources and associated settings. As an {{ecloud}} user, you can be a member of multiple organizations. * [](/cloud-account/join-or-leave-an-organization.md) -* [View and switch between organizations](/cloud-account/switch-organizations.md) +* [](/cloud-account/switch-organizations.md) ## Customize your interface diff --git a/cloud-account/join-or-leave-an-organization.md b/cloud-account/join-or-leave-an-organization.md index b2327fb4ed..1908e6a7b4 100644 --- a/cloud-account/join-or-leave-an-organization.md +++ b/cloud-account/join-or-leave-an-organization.md @@ -13,12 +13,16 @@ products: # Join or leave an organization -Organizations in {{ecloud}} group user accounts, projects and deployments under a common billing and access structure. If you have been invited to an organization, you can accept the invitation and become a member. You can join multiple organizations, or [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). +Organizations in {{ecloud}} group user accounts, projects, and deployments under a common billing and access structure. If you have been invited to an organization, you can accept the invitation and become a member. You can join multiple organizations, or [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). -You can also leave an organization at any time, as long as you don’t have active projects or deployments associated with your account. +You can also leave an organization, with some restrictions. Refer to [Leave an organization](#ec-leave-organization) for details. This guide explains how to join or leave an organization. To learn how to view organizations you have access to and switch between them, refer to [](switch-organizations.md). +:::{tip} +If you're an organization owner or admin, refer to [](/deploy-manage/cloud-organization/manage-multiple-organizations.md) to learn how to manage multiple organizations. +::: + ## Accept an invitation [ec-accept-invitation] When you're invited to join an organization, you receive an email with a link to accept the invitation. Invitations expire after 72 hours. If you don't accept within that period, an administrator of the organization needs to send a new invitation. Refer to [manage users](/deploy-manage/users-roles/cloud-organization/manage-users.md) for more information. diff --git a/cloud-account/switch-organizations.md b/cloud-account/switch-organizations.md index 5ad540a732..79a5eec16c 100644 --- a/cloud-account/switch-organizations.md +++ b/cloud-account/switch-organizations.md @@ -5,10 +5,10 @@ applies_to: serverless: ga products: - id: cloud-hosted -navigation_title: Switch between organizations +navigation_title: View and switch between organizations --- -# Switch between {{ecloud}} organizations +# View and switch between {{ecloud}} organizations From a single {{ecloud}} account, you can access multiple organizations. @@ -25,6 +25,12 @@ If you're an organization owner, then you can learn more about managing multiple To join an additional organization, [accept an invitation](/cloud-account/join-or-leave-an-organization.md#ec-accept-invitation) to join the organization. You can also [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). ::: +:::{include} /deploy-manage/cloud-organization/_snippets/view-orgs.md +::: + +:::{include} /deploy-manage/cloud-organization/_snippets/switch-orgs.md +::: + ## Log in with multiple organizations When you belong to multiple organizations, the login experience depends on whether your browser has information about the organization you most recently used: @@ -34,10 +40,4 @@ When you belong to multiple organizations, the login experience depends on wheth If your last used organization enforces a specific login method (such as SAML SSO), you're directed to that login flow automatically. -If you log out, your browser remembers which organization you last used. The next time you log in, you're directed to the appropriate login page for that organization. - -:::{include} /deploy-manage/cloud-organization/_snippets/view-orgs.md -::: - -:::{include} /deploy-manage/cloud-organization/_snippets/switch-orgs.md -::: \ No newline at end of file +If you log out, your browser remembers which organization you last used. The next time you log in, you're directed to the appropriate login page for that organization. \ No newline at end of file diff --git a/deploy-manage/cloud-organization/manage-multiple-organizations.md b/deploy-manage/cloud-organization/manage-multiple-organizations.md index e4d0c15e47..dfd7f9ec03 100644 --- a/deploy-manage/cloud-organization/manage-multiple-organizations.md +++ b/deploy-manage/cloud-organization/manage-multiple-organizations.md @@ -20,6 +20,10 @@ You might want to create multiple organizations for reasons such as the followin Although you can access multiple organizations from the same {{ecloud}} account, each organization is independent. Each organization has its own set of resources, users, settings, and billing and licensing. Because of this, you need to be logged in to the organization you want to manage to make changes to its resources and settings. +:::{tip} +This page covers admin tasks for managing organizations. To learn about joining, viewing, switching between, or leaving organizations as a member, refer to [](/cloud-account/join-or-leave-an-organization.md) and [](/cloud-account/switch-organizations.md). +::: + You can perform the following tasks to manage multiple organizations: * [Create a new organization](#create-a-new-organization) From f335370e8c99492215882b1062f1e7cadf9d14ad Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 24 Jun 2026 16:41:53 -0400 Subject: [PATCH 15/19] little polishes --- cloud-account/update-your-email-address.md | 4 ++++ .../cloud-organization/_snippets/switch-orgs.md | 6 +++++- .../elastic-cloud/marketplace-trial-conversion.md | 14 +++++++------- 3 files changed, 16 insertions(+), 8 deletions(-) diff --git a/cloud-account/update-your-email-address.md b/cloud-account/update-your-email-address.md index f53585ba31..ef9fc1ff58 100644 --- a/cloud-account/update-your-email-address.md +++ b/cloud-account/update-your-email-address.md @@ -14,6 +14,10 @@ products: Each {{ecloud}} account has a primary email associated with it. By default, the primary email address is used to sign up for {{ecloud}} and to log in. If needed, you can change this primary email address. Your email address is used to uniquely identify you. It can’t be used for more than one {{ecloud}} account, whether that account is a trial account, a standard {{ecloud}} account, or a subscription account through a marketplace. However, a single {{ecloud}} account can belong to [multiple organizations](/cloud-account/switch-organizations.md). + +:::{tip} +If you have separate {{ecloud}} accounts for different organizations and want to consolidate to a single account, ask an organization owner in each organization to [reconcile your accounts](/deploy-manage/cloud-organization/manage-multiple-organizations.md#reconcile-alternative-email-addresses). +::: ## Change your email address (native sign-in) diff --git a/deploy-manage/cloud-organization/_snippets/switch-orgs.md b/deploy-manage/cloud-organization/_snippets/switch-orgs.md index aea6b9684a..81d465fde8 100644 --- a/deploy-manage/cloud-organization/_snippets/switch-orgs.md +++ b/deploy-manage/cloud-organization/_snippets/switch-orgs.md @@ -5,4 +5,8 @@ You can switch between organizations at any time. Depending on the authenticatio 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). 2. From the top navigation menu, click on the user menu and select **Profile**. 3. Click the **My organizations** tab. -4. Click the name of the organization you want to switch to. If it doesn't appear in the list, click **Manage organizations** to view all of the organizations you have access to. \ No newline at end of file +4. Click the name of the organization you want to switch to. If it doesn't appear in the list, click **Manage organizations** to view all of the organizations you have access to. + +:::{tip} +You can also switch organizations from the breadcrumbs at the top of any page. Click your current organization name and select another organization from the list. +::: \ No newline at end of file diff --git a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md index 67215d1b31..42bac5fbd1 100644 --- a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md +++ b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md @@ -42,17 +42,17 @@ Go to the [{{ecloud}} listing on the {{gcp}} Marketplace](https://console.cloud. :::::{step} Sign in with your existing credentials When prompted to create a new account or sign in, choose to **sign in** with your existing {{ecloud}} credentials. ::::: -:::::{step} Select the organization to convert -What happens next depends on how many organizations your account belongs to: +:::::{step} Select the organization to upgrade +The upgrade page shows the cloud provider account that the subscription will be linked to. Confirm this is the correct account before continuing. -- **Single convertible trial organization:** You are presented with an option to convert the trial to the marketplace subscription. Billing through the marketplace begins immediately upon conversion. -- **Multiple organizations:** You are shown a list of your organizations. Organizations that are eligible for conversion have a **Convert** option. Select the organization you want to convert. +What happens next depends on how many organizations your account belongs to: -You can also choose to **create a new organization** instead of converting an existing one. The new organization starts with its own 7-day marketplace trial. +- **Single convertible trial organization:** You are presented with an option to upgrade the trial to the marketplace subscription. Billing through the marketplace begins immediately upon upgrade. +- **Multiple organizations:** You are shown a list of your eligible organizations. Click the organization you want to upgrade. To also see organizations that aren't eligible, toggle **Show non-convertible organizations**. -% TODO: confirm CTA labels from Figma +You can also choose to **create a new organization** instead of upgrading an existing one. The new organization starts with its own 7-day marketplace trial. -If none of your existing organizations are eligible for conversion, you can still create a new organization through the marketplace, or refer to [Which organizations can be converted](#ec-marketplace-conversion-candidates) to understand why. +If none of your existing organizations are eligible for upgrading, you can still create a new organization through the marketplace, or refer to [Which organizations can be converted](#ec-marketplace-conversion-candidates) to understand why. ::::: :::::: From 916128a68d5d1bc9c9b78b3b8b49fb40880c9c2e Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 24 Jun 2026 17:13:08 -0400 Subject: [PATCH 16/19] email change limitation --- cloud-account/update-your-email-address.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/cloud-account/update-your-email-address.md b/cloud-account/update-your-email-address.md index ef9fc1ff58..39ac119d2a 100644 --- a/cloud-account/update-your-email-address.md +++ b/cloud-account/update-your-email-address.md @@ -15,10 +15,12 @@ Each {{ecloud}} account has a primary email associated with it. By default, the Your email address is used to uniquely identify you. It can’t be used for more than one {{ecloud}} account, whether that account is a trial account, a standard {{ecloud}} account, or a subscription account through a marketplace. However, a single {{ecloud}} account can belong to [multiple organizations](/cloud-account/switch-organizations.md). -:::{tip} If you have separate {{ecloud}} accounts for different organizations and want to consolidate to a single account, ask an organization owner in each organization to [reconcile your accounts](/deploy-manage/cloud-organization/manage-multiple-organizations.md#reconcile-alternative-email-addresses). + +:::{note} +If you belong to any organization that enforces a specific authentication method (such as SAML SSO, Google Sign-In, or Microsoft Sign-In), you can't change your primary email address using the procedures on this page. This restriction applies even if other organizations you belong to don't enforce a login method. ::: - + ## Change your email address (native sign-in) If you log in using a standard email and password, follow these steps to update your email address: From 2c99d3c1caaa0dfcc5e11c56b52a07af3ec80d61 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Thu, 25 Jun 2026 16:25:04 -0400 Subject: [PATCH 17/19] Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- cloud-account/switch-organizations.md | 2 ++ deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md | 2 +- .../deploy/elastic-cloud/marketplace-trial-conversion.md | 1 + 3 files changed, 4 insertions(+), 1 deletion(-) diff --git a/cloud-account/switch-organizations.md b/cloud-account/switch-organizations.md index 79a5eec16c..489ebd667d 100644 --- a/cloud-account/switch-organizations.md +++ b/cloud-account/switch-organizations.md @@ -5,7 +5,9 @@ applies_to: serverless: ga products: - id: cloud-hosted + - id: cloud-serverless navigation_title: View and switch between organizations +description: Learn how to view all Elastic Cloud organizations you belong to, switch between them, and understand the login experience when you have multiple organizations. --- # View and switch between {{ecloud}} organizations diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md index e914952a61..bb064fa538 100644 --- a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md @@ -103,7 +103,7 @@ You have a few options to access your deployment or project: ## Multi-org accounts and the Azure portal [ec-azure-multi-org-limitations] -Unlike {{aws}} and {{gcp}}, the Azure portal does not provide an organization picker during resource creation. When your account has a single organization, the Azure portal automatically adds new resources to that organization and can handle trial conversion. When your account has multiple organizations, the portal may not be able to determine which organization to target. +Unlike {{aws}} and {{gcp}}, the Azure portal does not provide an organization picker during resource creation. When your account has a single organization, the Azure portal automatically adds new resources to that organization and can handle trial conversion. When your account has multiple organizations, the portal might not be able to determine which organization to target. The following limitations apply: diff --git a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md index 42bac5fbd1..75d6dc9d5d 100644 --- a/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md +++ b/deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md @@ -5,6 +5,7 @@ applies_to: serverless: ga products: - id: cloud-hosted +description: Learn how to convert an existing Elastic Cloud trial to an AWS, Azure, or GCP marketplace subscription. --- # Convert a trial to a marketplace subscription [ec-marketplace-trial-conversion] From 5458f69da41fda85fc854fe3ba3e4d6d25c08dde Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Fri, 26 Jun 2026 14:30:04 -0400 Subject: [PATCH 18/19] Update cloud-account/join-or-leave-an-organization.md Co-authored-by: Alex Chalkias <34575586+alxchalkias@users.noreply.github.com> --- cloud-account/join-or-leave-an-organization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloud-account/join-or-leave-an-organization.md b/cloud-account/join-or-leave-an-organization.md index 1908e6a7b4..5392167071 100644 --- a/cloud-account/join-or-leave-an-organization.md +++ b/cloud-account/join-or-leave-an-organization.md @@ -41,7 +41,7 @@ To decline an invitation, you can ignore the email. The invitation expires autom ## Leave an organization [ec-leave-organization] -You can leave an organization at any time, as long as you are a member of at least one other organization. If you are the only owner of an organization, you must transfer ownership before leaving. +You can leave an organization at any time. If you are the only owner of an organization, you must transfer ownership before leaving. You can leave only the organization you're currently signed in to. To leave a different organization, [switch to it](/cloud-account/switch-organizations.md) first. From 398e23d747e9e187cf10e2dba3432be99e7ce310 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Fri, 26 Jun 2026 14:39:31 -0400 Subject: [PATCH 19/19] remove sign up with existing email process --- cloud-account/update-your-email-address.md | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/cloud-account/update-your-email-address.md b/cloud-account/update-your-email-address.md index 39ac119d2a..5228cbcc70 100644 --- a/cloud-account/update-your-email-address.md +++ b/cloud-account/update-your-email-address.md @@ -41,19 +41,4 @@ If you log in using Google or Microsoft Sign-In, follow these steps to update yo ## Changing your email address with a Microsoft Marketplace account -If your organization is associated with [Microsoft Marketplace](../deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md), you can’t change your primary email address using the above methods. Instead, [invite another user](../deploy-manage/users-roles/cloud-organization/manage-users.md) with the desired email address to join your organization. - -## Sign up using an existing email address [sign-up-existing] - -% is this still needed at all? - -In some situations, you might want to create a new {{ecloud}} account using an email address that is already associated with an existing account. To sign up to {{ecloud}} using an email address associated with another {{ecloud}} account, you must remove the email address from your previous account and replace it with a new address. - -:::{note} -You don't need to follow this procedure if you want to [join an additional organization](/cloud-account/join-or-leave-an-organization.md) or [create a new organization](/deploy-manage/cloud-organization/manage-multiple-organizations.md#create-a-new-organization). One account can belong to and own multiple organizations. -::: - -1. Use your current email address (for example, `my.preferred.address@foobar.com`) to log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. Follow the steps from one of the procedures on this page to update that email address to another email address, such as `my.alternate.address@gmail.com`. - -You can now use the email address from step 1 to [sign up for a new account](/deploy-manage/deploy/elastic-cloud/create-an-organization.md). \ No newline at end of file +If your organization is associated with [Microsoft Marketplace](../deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md), you can’t change your primary email address using the above methods. Instead, [invite another user](../deploy-manage/users-roles/cloud-organization/manage-users.md) with the desired email address to join your organization. \ No newline at end of file