How does the license expiry affect the Chef Infra Server?

What happens to Chef Infra Server and Chef Infra Client after the Chef Automate license expires?

Will Chef Client runs keep working, or will they fail, especially if the Infra Server is embedded in Automate?

This is for Chef Infra Server embedded with Chef Automate?

In deployments where the Chef Infra Server is embedded in Chef Automate, Chef Infra Client runs stop working once license enforcement begins. The client binary is not licensed by Automate, but it cannot complete a run without a functioning Infra Server. A standalone Infra Server with its own license is not affected by an Automate license lapse.

How does the license expiry affect the Chef Infra Server?

When the Infra Server is embedded in Automate, it falls under the same license boundary as Automate. Once enforcement begins, the server stops responding normally to client and admin requests. You can expect:

• knife commands fail to authenticate or connect
• chef-server-ctl commands stop working or return restricted behavior
• Node registration and API calls fail
• Cookbook uploads and downloads fail
• Data collection and reporting to Automate stop

Why does Chef Infra Client fail?

Chef Infra Client has no license check of its own, so the binary stays on the node and can still be run. But every converge depends on the Infra Server for:

• Node authentication and registration
• Cookbooks and policy data
• Roles, environments, and data bags
• Run status and reporting

When the server stops accepting requests, the converge fails. Typical symptoms are:

• 401 or 403 authentication errors
• Connection timeouts
• Failed cookbook downloads
• "Node not found" errors
• Failed reporting or data collection

Is there a grace period?

It depends on the license type:

What is the scope of the impact?

The impact goes beyond the UI and reporting layer. In an embedded setup, core server functionality is affected too:

• The UI may fail to load or show only limited data
• Reporting and compliance workflows are disrupted
• Ingest pipelines and API integrations become unreliable or fail
• Every Chef Infra Client run that depends on the server fails

Does a standalone Infra Server behave differently?

Yes. A standalone Chef Infra Server with its own separate license is not governed by the Automate license, so an Automate expiry does not automatically affect it or the clients that use it.

Recommendation - What should you do before the license expires?

1. Confirm whether your Infra Server is embedded in Automate or standalone.
2. Record the license expiry date and start renewal well ahead of it.
3. Apply the renewed license before the grace period ends.
4. Before the renewal date, verify that knife, chef-client, and the server APIs work, so you have a baseline to compare against.

Final conclusion

Short version: in an Automate-managed setup, Chef Client does not continue to work normally after the Automate license expires because the embedded Chef Infra Server becomes non-functional or restricted.

This is the key operational risk: once the license expires, the infrastructure layer that Chef Client depends on starts failing, so the client runs fail as a downstream effect.

Important contractual clarification

Technical Support does not determine contract terms, renewal status, licensing entitlements, or grace periods. Those are governed by the commercial agreement and licensing terms associated with your purchase. Contact your Account Manager for more details. 

To be clear, if the licenses are not renewed and a replacement license is not applied before the expiration date, Chef will cease operating when the license expires.

This means that any support conversation, status check, or renewal estimate is informational only. The actual legal and operational status of the license is defined by the signed agreement and the license terms.