HCP Changelog

Users who log in through GitHub or with email and password can now remove their own HCP accounts directly from the portal without filing a support ticket.

Vault 2.0 has started rolling out to HCP Vault Dedicated clusters on AWS and Azure, with the 2.0.4 capabilities documented in the HCP Vault Dedicated changelog.

When inviting users to your organization, you can now assign access at the organization or project level upfront, eliminating follow-up permission changes and letting new users start with the permissions they need.

HCP Organizations: Organization owners can now delete their HCP organization directly in the HCP Portal. Once all items in the deletion checklist are resolved, owners can initiate deletion without opening a support ticket.

Organization owners can now delete their HCP organization directly in the HCP Portal once all items in the deletion checklist are resolved, without opening a support ticket.

HCP Organizations: Enterprise constraints are now available for centralized governance and cost control. Organization administrators can restrict which HCP products (Vault, Boundary, Vault Radar, Packer, Waypoint, Vagrant) users may deploy within their organization,…

Organization administrators can now restrict which HCP products (Vault, Boundary, Vault Radar, Packer, Waypoint, Vagrant) users may deploy within their organization, providing preventative controls that apply regardless of individual user permissions.

Deleting an organization's SSO connection now deletes all SSO users from the organization. Suspending an SSO connection does not trigger user deletion.

HCP Access Management: When an HCP organization's SSO connection is deleted, HCP will now delete all SSO users from the organization. Suspending an SSO connection will not result in HCP deleting SSO users from the organization.

Vault 2.0.3 has started rolling out to HCP Vault Dedicated clusters on AWS and Azure.

HCP Vault 2.0.3 for AWS and Azure: Vault 2.0 has started rolling out to HCP Vault Dedicated clusters on AWS and Azure.

SCIM provisioning: HCP now supports SCIM (System for Cross-domain Identity Management) provisioning for automated user and group lifecycle management. With SCIM enabled, you can automatically sync user and group changes from your identity provider to HCP, including: user…

HCP now supports SCIM (System for Cross-domain Identity Management) provisioning for automated user and group lifecycle management. With SCIM enabled, you can automatically sync user and group changes from your identity provider to HCP, including:

HCP Vault 2.0 for AWS and Azure: Vault 2.0 has started rolling out to HCP Vault Dedicated clusters on AWS and Azure.

Vault 2.0 has started rolling out to HCP Vault Dedicated clusters on AWS and Azure. Refer to HCP Vault Dedicated changelog to learn more about Vault 2.0 capabilities available to HCP Vault.

A self-service organization deletion checklist is now available for organization owners. The checklist provides an automated pre-flight check to verify that all prerequisites—such as decommissioning active resources, resolving billing requirements, and clearing IAM…

HCP Organizations: A self-service organization deletion checklist is now available for organization owners. The checklist provides an automated pre-flight check to verify that all prerequisites—such as decommissioning active resources, resolving billing requirements, and…

Organization owners now get an automated pre-flight checklist verifying prerequisites like decommissioned resources, resolved billing, and cleared IAM configurations before an organization can be deleted, reducing manual support tickets.

A self-service checklist now verifies prerequisites—decommissioning active resources, resolving billing requirements, and clearing IAM configurations—before organization deletion, reducing manual support tickets.

Vault 1.21.3 has started rolling out to HCP Vault Dedicated clusters on AWS and Azure. Refer to 1.21.3 Enterprise release notes in GitHub to learn more about what's new in 1.21.3.