Fortinet Grace Period Policy Explained

Why Your License Starts Before You Do

Fortinet service contracts — including FortiCare support, FortiGuard subscriptions, and bundled licenses — start counting down whether you register them or not. If you’ve ever activated a new FortiGate only to discover your 1-year subscription shows 10 months remaining, this is why. Fortinet’s grace period policy automatically starts your license after a set number of days, even if the device is still sitting in a box.

This catches a lot of customers off guard. Here’s how the policy actually works, what the deadlines are, and what you can do about it.

What Is the Fortinet Grace Period?

The grace period is the number of days Fortinet gives you to register a service contract before it automatically activates. Once that window closes, the subscription term starts on its own — backdated to the end of the grace period — whether you’ve plugged the device in or not. Your remaining subscription time is whatever is left after those lost days.

This applies to every term-based Fortinet service: FortiCare Premium support, FortiGuard security subscriptions (UTP, ATP, etc.), SaaS licenses, FortiClient subscriptions, FortiCloud management, and everything sold as part of a hardware bundle.

Grace Period Timelines — the Numbers That Matter

The exact grace period depends on what you bought and where it was shipped:

The Scenario That Frustrates Everyone

Here’s a real-world example. You order a FortiGate 30G with a 5-year UTP bundle for a branch office. The project gets delayed — construction runs late, the rack isn’t ready, whatever the reason. The box sits in your stockroom for three months.

When you finally unbox and register it in FortiCloud, you see this: your 5-year FortiCare subscription shows 4 years and 10 months remaining. Two months just vanished — because the 60-day grace period (Canada) expired after month two, and the contract auto-started on day 61.

You didn’t do anything wrong. You just didn’t know the clock was ticking.

Why Does Fortinet Do This?

From Fortinet’s perspective, the grace period exists to give you a reasonable window to deploy and register. But it also prevents distributors and resellers from stockpiling licenses indefinitely — sitting on a 3-year contract for a year before activating it, effectively turning it into a 4-year term. The auto-start mechanism keeps the economics predictable for everyone in the supply chain.

That said, the communication around this policy is often poor. It’s buried in legal terms, rarely flagged at the point of sale, and the first time most IT admins hear about it is when they see a shorter-than-expected subscription in their FortiCloud dashboard.

What You Should Do

• Register immediately after purchase. Don’t wait for the deployment. As soon as you receive a FortiGate, FortiSwitch, FortiAP, or any Fortinet product with a service contract, log into FortiCloud and register the serial number. This starts the clock on YOUR terms, not Fortinet’s auto-start timer.
• If you’re ordering ahead of deployment, plan for the grace period. Have a 90-day project timeline? You’re fine in most regions, but cutting it close in Canada and the US (60 days). If delay is likely, consider ordering closer to deployment.
• Check your existing devices. Log into FortiCloud and verify that your subscription end dates match what you expected. If something looks short, the grace period auto-start is almost certainly why.
• Training and professional services — use them or lose them. These have a 365-day grace period, but there’s no auto-start safety net for 1-year contracts. If you don’t register and consume them within a year, they’re gone. Multi-year contracts are slightly more forgiving — only the first year is forfeited.

Bundles vs. Standalone Licenses — Same Rules Apply

Whether you buy a FortiGate 90G UTP bundle (hardware + FortiCare + FortiGuard in one SKU) or purchase the hardware and FortiCare separately, the grace period policy applies to every service contract in exactly the same way. A bundle doesn’t give you extra time — all the attached service contracts share the same auto-start deadline tied to the shipment date.

Renewing When Fortinet Changes the SKU — FortiGate Cloud to FortiManagement Cloud

Fortinet periodically retires SKUs and replaces them with new ones — even when the underlying service continues. A common case right now: FortiGate Cloud management subscriptions are being replaced by FortiManagement Cloud SKUs. If your device currently runs a FortiGate Cloud license and it’s time to renew, the renewal SKU will be a FortiManagement Cloud part number instead.

This raises a fair question: if I buy the new SKU now, does it start immediately and overlap with my existing license? Or does it queue up after the current one expires?

Fortinet confirmed that the new FortiManagement Cloud SKU is treated as a renewal and continuation of the existing FortiGate Cloud subscription. You can safely purchase and register the new SKU before your current license expires — the new term begins the day after the current license ends, with no overlap and no lost subscription time.

The key is in the SKU structure. A renewal SKU like FC-10-MGT4G-131-02-12 contains -02- before the term code (-12 for 12 months). That -02- tells Fortinet’s system to extend the license after the current one expires, rather than starting a new term immediately. This is the same mechanism that applies to all Fortinet renewal contracts — the SKU itself encodes the start-date behavior.

The Official Policy

Fortinet publishes the full Service Contract Activation and Grace Period Policy on their legal page. It covers edge cases like Enterprise Agreements (exempt), renewals with predefined start dates (exempt), and perpetual licenses (exempt). If you have a complex multi-site deployment with staggered delivery, it’s worth reading in full.