Terraform support encompasses the formal channels, diagnostic procedures, and version policy decisions that govern how organizations maintain reliability when using HashiCorp Terraform for infrastructure as code. Support responsibilities differ between open-source Terraform core, Terraform Enterprise, and cloud provider integration scenarios such as Azure. The following guide covers how to engage HashiCorp support, how to collect and deliver diagnostic artifacts, how version support and lifecycle work for Terraform releases, and how Azure providers interact with supported Terraform versions.
Terraform Enterprise Support Engagement
If some aspect of Terraform Enterprise is not working as expected, please reach out to support for help.
You can engage HashiCorp support via the web portal at https://support.hashicorp.com or by email at [email protected]. Please make sure to use your organization email (not your personal email) when contacting us so we can associate the support request with your organization and expedite our response.
For most technical issues, HashiCorp support will ask you to include diagnostic information in your support request. To ensure the required information is included, Terraform Enterprise can automatically generate a support bundle including logs and configuration details.
Provide the following information with any support requests:
- Deployment runtime, such as Docker or Kubernetes.
- Deployment cloud service, such as AWS, AzureRM, GCP, or your local data center.
- Operational mode, such as
disk
orexternal - Your support bundle
The support bundle contains logging and telemetry data from various components in Terraform Enterprise. It may also include log data from Terraform builds you have executed on your Terraform Enterprise installation.
Uploading the support bundle is performed through secure channels. Attach the bundle to your support ticket. If possible, use the SendSafely integration available in the support portal at support.hashicorp.com, as it allows for large file uploads.
If you are unable to use the integration in the portal, please upload directly to https://hashicorp.sendsafely.com/u/ptfe-support-bundles.
Pre-sales customers should upload support bundle files directly to https://hashicorp.sendsafely.com/u/ptfe-support-bundles.
SendSafely lets you upload large file.
Diagnostics and Support Bundle Collection
Diagnostic information is available via in the installer dashboard on port 8800 of your installation.
Note: For Terraform Enterprise Active/Active implementations the installer dashboard is disabled.
For Terraform Enterprise Active/Active implementations the installer dashboard is disabled. Instead, you can generate and save support bundles to your configured object storage location by executing the tfe-admin support-bundle command on a node instance from every node in the cluster.
On the dashboard, click on the Support tab:
On the next page, click Download Support Bundle to download the support bundle directly to your web browser.
Once you have downloaded your support bundle, please use a secure method to upload it to HashiCorp support.
If Terraform Enterprise is deployed to the legacy Replicated runtime, you can access diagnostic information in the installer dashboard or on port 8800 of your installation.
The installer dashboard is disabled for Replicated deployments in active-active mode. Instead, you can generate and save support bundles to your configured object storage location by executing the tfe-admin support-bundle command on a node instance from every node in the cluster.
Support bundles can instead be generated and saved to the configured object storage location by executing this command from the command line on a node instance:
tfe-admin support-bundle
This will create a support bundle from every node in the cluster.
On the dashboard, click on the Support tab:
On the next page, click the Download Support Bundle button which will download the support bundle directly to your web browser.
Support Bundle Access Methods by Deployment
| Deployment scenario | Access method | Command |
|---|---|---|
| Standard installation | Installer dashboard on port 8800 | UI Download Support Bundle |
| Active/Active | Installer dashboard disabled | tfe-admin support-bundle |
| Legacy Replicated runtime | Installer dashboard or port 8800 | UI Download Support Bundle |
| Replicated active-active | Installer dashboard disabled | tfe-admin support-bundle per node |
The command line approach is essential for clustered and active-active topologies where the web dashboard is intentionally disabled to avoid split-brain operations.
Terraform Version Support and Lifecycle
How Does Terraform Handle Version Support and Lifecycle?
HashiCorp supports Generally Available releases of Terraform for up to two years.
Eligible code fixes and hot fixes are provided via a new minor release on top of the latest major release branch, for up to two releases from the most current major release.
Staying within this window ensures you continue to receive minor version updates.
Q2: Does Terraform have traditional LTS versions?
No. Terraform uses a consistent 2-year support window per GA release rather than long-term support branches. Fixes come through minor releases on the active major branches.
Q3: What happens if I stay on a Terraform version older than the supported two major releases?
You will no longer receive code fixes or hot fixes, and newer providers may drop compatibility, leading to plan or apply failures.
Q4: How often do most teams upgrade Terraform?
Experienced teams typically upgrade every 6-12 months or when a required provider demands a newer core version.
Q5: Where can I read the official Terraform support policy?
See the HashiCorp Support Period and End-of-Life Policy for full details on how fixes are delivered across major release branches.
The version policy has practical implications for CI/CD pipelines, provider selection, and enterprise change control. Because there are no traditional LTS versions, organizations must plan regular upgrades rather than pinning to a long-term branch.
| Policy element | Detail |
|---|---|
| Support window | Up to two years for Generally Available releases |
| Fix delivery | Minor release Z on latest major release branch |
| Coverage | Up to two releases from most current major release |
| LTS | No traditional LTS versions |
| Upgrade cadence | 6-12 months typical |
Azure Provider Interaction and Support Considerations
Hashicorp Terraform is an open-source IaC tool for configuring and deploying cloud infrastructure. It codifies infrastructure in configuration files that describe the desired state for your topology. Terraform enables the management of any infrastructure - such as public clouds, private clouds, and SaaS services - by using Terraform providers.
There are several Terraform providers that enable the management of Azure infrastructure:
- AzureRM: Manage stable Azure resources and functionality such as virtual machines, storage accounts, and networking interfaces.
- AzAPI: Manage Azure resources and functionality using the Azure Resource Manager APIs directly. Enables consistency with Azure's latest and greatest functionality without requiring provider updates
AzureRM remains the stable, widely adopted provider for mainstream Azure resources. AzAPI provides direct access to Azure Resource Manager APIs, allowing usage of new Azure features before provider updates are released. This distinction matters for support scenarios because AzAPI reduces provider version coupling while increasing responsibility for API correctness in user configuration.
When filing support for Azure related Terraform issues, the deployment cloud service should be specified as AzureRM or Azure. The runtime details, such as Docker or Kubernetes, and operational mode such as disk or external, help support engineers reproduce environment specific failures.
Best Practices for Support Requests
Effective Terraform Enterprise support requests include precise environment context and a complete support bundle.
- Use an organization email when contacting [email protected] to ensure automatic association with your organization.
- Include deployment runtime, cloud service, and operational mode in the initial ticket description.
- Generate a support bundle before contacting support to avoid delays.
- For active-active clusters, run tfe-admin support-bundle on each node and collect artifacts to object storage before upload.
- Use the SendSafely integration in the HashiCorp support portal for large bundles. If unavailable, upload to the designated secure URL.
- For pre-sales inquiries, upload bundles directly to the pre-sales SendSafely location.
- Keep Terraform core within the two-year support window to ensure fixes and provider compatibility.
Conclusion
Terraform support is a structured process that combines formal engagement channels with diagnostic artifact collection and version lifecycle awareness. HashiCorp support for Terraform Enterprise is accessed via the web portal at https://support.hashicorp.com or by email at [email protected] using an organization email. Diagnostic data is delivered via support bundles generated through the installer dashboard on port 8800 or via the tfe-admin support-bundle command for active-active and Replicated deployments. The support bundle contains logging and telemetry data from various components in Terraform Enterprise and may include log data from Terraform builds executed on the installation.
Version support follows a two-year window for Generally Available releases with fixes delivered as minor releases on active major branches. There are no traditional LTS versions, and teams that remain beyond two major releases lose code fixes, hot fixes, and provider compatibility. Experienced teams upgrade every 6-12 months or when a provider requires a newer core.
Azure integration adds provider choice between AzureRM for stable resources and AzAPI for direct ARM API access. Both options are influenced by Terraform core version support, making version hygiene and timely upgrades critical for stable Azure infrastructure management. Combining accurate support request information, timely bundle generation, and adherence to the version support policy reduces mean time to resolution and maintains infrastructure reliability.