Current + Fortinet FortiCloud integration

Fortinet's FortiCloud holds the registration record for every unit an MSP has registered: the serial, the model, and the date support runs out. Current's Fortinet integration is a view-only feed from that record into the SBR/QBR module and the company page. It reads what FortiCloud already knows and never writes back.

What the integration does

Current authenticates to FortiCloud with a read-only IAM API user, walks the registered estate every six hours, and stages the result as evidence for AI-assisted Strategic Business Reviews. The support dates are already on the company record when an account manager opens it, rather than being assembled the week of the review.

What data flows

• Registered assets — every Fortinet serial with its product model, the label typed in FortiCloud, the registration date, and whether the unit is decommissioned. FortiGate, FortiSwitch, FortiAP, FortiMail, FortiAnalyzer and the rest all register here.
• Support entitlement — the latest entitlement end date on each unit, the level and type behind it, and a state of covered, expiring within 60 days, or expired.
• Contracts — the contract number, the latest contract term end date, and the SKU a renewal quote is built from.
• Product-model lifecycle — end of support and end of renewal for the model, which is a replacement conversation rather than a renewal one.
• Partner groupings — the FortiCloud folder or account each asset belongs to, matched to a Current company so every date above lands on the right record.

The feed is one-way. Current does not register serials, consume licence codes, download licence keys, edit asset details, manage folders, or decommission units. Those endpoints are not in the connector's code, so they cannot be reached by a bug either. FortiCloud stays the system of record; Current uses the evidence.

An expired firewall is a security fact

A Fortinet unit whose entitlement lapses stops receiving FortiGuard updates. That is why this feed sits in the security posture chapter of a review rather than in an inventory appendix: the sentence a partner needs to hear is that the box guarding their network stopped getting threat updates in March, and the sentence an account manager needs is the SKU that fixes it.

The latest date wins

A FortiGate usually carries several entitlements at once — a hardware warranty, FortiCare, a UTP bundle — expiring on different days. Current reads the latest of them, so a unit whose hardware warranty lapsed while its FortiCare subscription runs another year shows as covered. Reading the earliest instead would flag a large share of a healthy estate as expired on the first sync, which is the kind of number that costs a review its credibility.

Unknown reads as unknown

Fortinet's asset search takes a date filter, and a unit carrying no entitlement date at all may not be returned by it. Current shows those as having no entitlement date on file: they never count as covered, never count as expired, and never raise an alert. The card counts assets with a known entitlement date rather than claiming a complete inventory, because a coverage percentage built by treating silence as a pass is one you cannot defend when a partner asks which units it covers.

Matching FortiCloud groupings to companies

Fortinet publishes no endpoint that lists partners; its multi-tenancy is account- and folder-shaped. Current works the roster out from the assets: an asset folder when FortiCloud returns one, otherwise the account, otherwise a single bucket. Groupings pair with companies by normalized name — punctuation and Inc/LLC/Ltd-style suffixes stripped — and only when exactly one company matches. Where two companies could both be the answer, the grouping waits on an unmapped list for a person to decide. An MSP that registers everything into one flat account sees a single row to map, which is a correct reading of that estate.

Where the data appears

• In Strategic Business Reviews, in the fleet and network chapter alongside your other network feeds such as Cisco Meraki and UniFi.
• On the company record, in the network estate card, as a renewal list sorted soonest first with the contract SKU beside each date.
• In dashboard metrics, as devices under support and support expiring across the book.
• In the company alert band, when a mapped company has a unit out of support or expiring inside 60 days.

Why it matters

Renewals are the part of a business review most often reconstructed by hand, because the dates live in a vendor portal and the review lives somewhere else. An MSP managing Fortinet gear for a partner like Northwind Traders can open the account and see that fourteen units are registered, twelve are covered, one FortiGate 100F loses its UTP bundle in seventy days, and one FortiSwitch is past the model's end of renewal and needs replacing rather than renewing — with the SKU for the first sitting next to the date. The renewal quote starts from a list instead of from a portal search.