Direct answer: what FortiMail Cloud Hosted is
Fortinet FortiMail Cloud Hosted is a cloud-delivered version of FortiMail in which Fortinet operates the service infrastructure while the customer retains email-security configuration and policy choices appropriate to the subscribed package. It is mainly used to inspect inbound and outbound email, reduce unwanted or malicious messages, apply layered threat controls, and support policy, reporting and message-handling requirements. Organisations with Microsoft 365, Google Workspace, Exchange or other supported email systems may consider it when they want a secure email gateway without owning FortiMail hardware or hosting a FortiMail VM. Before proceeding, confirm active mailbox count, protected domains, subscription tier, API integration requirements, mail routing, desired add-ons and the exact commercial SKU.
What the hosted service does
FortiMail Cloud Hosted places FortiMail email security in Fortinet-operated infrastructure rather than requiring the customer to purchase, rack, power and maintain a physical appliance or to provide virtual infrastructure. The service is designed to handle email security as a hosted gateway while retaining many of the policy and protection functions associated with FortiMail.
The platform can inspect inbound and outbound email and use multiple techniques to evaluate senders, domains, message content, attachments and URLs. Depending on the chosen offering, controls can include anti-spam, antivirus, outbreak protection, advanced malware analysis, URL click protection, impersonation analysis, content disarm and reconstruction, encryption and cloud mailbox integration. Buyers should treat these as package-dependent capabilities rather than assume every function is included in the entry service.
Who should consider it
The hosted model is suited to organisations that want dedicated email-security controls but prefer not to manage the compute, storage, platform availability and software infrastructure associated with a self-hosted FortiMail appliance or virtual machine. It can be useful for lean IT teams, multi-site businesses, organisations standardising on subscription services, and companies that require a scalable mailbox-based commercial model.
It may also fit enterprises already using Microsoft 365 or Google Workspace that need secure email gateway filtering and, where the correct premium package is selected, API-supported cloud-mail scanning and post-delivery actions. Organisations that require full ownership of the security appliance, specific on-premises data-handling arrangements or a customer-controlled virtual deployment should compare FortiMail hardware and VM options before choosing Hosted.
Business problems FortiMail Cloud Hosted can help address
Email security is rarely one problem. IT teams usually need to reduce nuisance mail, stop malicious content, identify impersonation, protect users from credential theft, monitor outbound information and keep legitimate communication flowing. The hosted service provides a way to address these concerns without operating the underlying FortiMail infrastructure.
Phishing and impersonation
Layered sender, reputation, content and impersonation analysis can help identify messages crafted to imitate executives, suppliers or trusted domains. Business verification processes remain important for payment and account-change requests.
Malicious files and URLs
Anti-malware, outbreak controls and advanced analysis can inspect attachments and links. Premium packages add capabilities such as cloud sandboxing and URL click protection, subject to the selected entitlement.
Unwanted bulk email
FortiMail combines sender reputation, authentication checks, protocol analysis and content inspection to reduce spam while allowing administrators to tune policy around legitimate business senders.
Infrastructure ownership
Hosted delivery removes the need to deploy and maintain FortiMail appliance or VM infrastructure. Customers still need to manage policies, integrations, mail-flow changes and operational processes appropriate to their environment.
Capability band: what changes by service tier
| Capability | Gateway | Gateway Premium | Premium with API Connector |
|---|---|---|---|
| AntiVirus, AntiSpam and virus outbreak service | Included | Included | Included |
| Cloud sandbox, URL click protection, CDR, impersonation analysis | Not shown as base Gateway features | Included in current ordering guide | Included |
| Cloud Email API integration for Microsoft/Google | Not included | Not included in standard Premium | Included |
| Image analysis and email continuity | Add-on | Add-on | Add-on |
Fortinet can change commercial bundles and SKU names over time. The table reflects current published FortiMail ordering guidance and should be used for selection planning, not as a substitute for a current quotation. FourTeck can confirm the applicable UAE SKU and term for the requested mailbox bracket.
Product-fit matrix
| Requirement | Suitable when | Confirm before ordering |
|---|---|---|
| Hosted secure email gateway | You want Fortinet to operate the service infrastructure. | Mail flow, domains, mailbox count, DNS and connector changes. |
| Advanced threat controls | You need sandboxing, click protection, CDR or impersonation analysis. | Premium service tier and included FortiGuard services. |
| Microsoft 365 or Google Workspace API support | You require mailbox scanning and post-delivery remediation beyond gateway mail flow. | Premium with API Connector, tenant permissions and supported integration design. |
| Large mailbox population | Annual per-mailbox licensing aligns with your procurement model. | Declared active mailbox count, pricing band, growth and subscription term. |
Licensing, compatibility and scope dependencies
FortiMail Cloud Hosted is not one universal SKU. Fortinet publishes several mailbox bands and service levels, and billing is based on the customer-declared number of active mailboxes. The quote therefore needs a reliable mailbox count rather than a rough employee count. Shared, service and functional mailboxes should be reviewed because the way they are treated can affect the declaration and commercial quantity.
The selected security tier matters just as much as mailbox quantity. Base Gateway provides core filtering and FortiGuard AntiVirus, AntiSpam and outbreak protection. Premium offerings add advanced controls such as cloud sandboxing, content disarm and reconstruction, click protection and impersonation analysis. API-based scanning and post-delivery clawback require the appropriate Cloud API Connector service. Optional services such as image analysis or email continuity should be quoted separately when needed.
Compatibility planning must cover the mail platform, DNS, accepted domains, third-party senders, connectors, TLS requirements and identity directory integration. A Microsoft 365 or Google Workspace project may require tenant permissions for API integration. An Exchange or hybrid environment can involve more complex routing and coexistence rules. Confirm the exact topology and change responsibilities before scheduling implementation.
A controlled purchase and deployment journey
Discover
Document active mailboxes, email platform, protected domains, daily and peak message flow, third-party senders, security policies and project constraints.
Select the Hosted tier
Decide whether core Gateway controls are sufficient or whether Premium, API Connector or additional services are required.
Build the quotation
Match the active-mailbox bracket, term, add-ons and implementation scope to the current Fortinet SKU structure for the UAE requirement.
Prepare mail flow
Plan DNS, connectors, accepted domains, SPF/DKIM/DMARC responsibilities, TLS, directory integration, API permissions and rollback steps.
Test and tune
Validate legitimate senders, quarantine workflows, policy actions, reporting and user communication before enforcing stricter controls broadly.
Three capabilities that change the buying decision
Layered gateway inspection
A secure email gateway must judge more than whether a file matches a known malware signature. FortiMail applies sender reputation, protocol and authentication checks, recipient validation, content inspection and multiple anti-spam techniques. This matters for businesses because many harmful messages are engineered to look ordinary: a fake supplier invoice, a domain that differs by one character, or a message containing a link rather than a malicious attachment. The hosted gateway can provide a dedicated decision layer before messages reach users, while outbound scanning can help detect malicious or inappropriate mail leaving the organisation. Administrators still need to tune trusted senders, third-party platforms and exceptions so business-critical messages are not interrupted.
Premium threat analysis and remediation
Premium Hosted packages add controls that matter when the threat model extends beyond basic spam and antivirus. Fortinet lists cloud sandboxing, content disarm and reconstruction, URL click protection and impersonation analysis in premium offerings. With the appropriate API Connector, the service can also support real-time and scheduled mailbox scanning and post-delivery clawback of newly discovered threats. These capabilities are useful for Microsoft 365 and Google Workspace environments where a message may need to be reassessed after delivery. The design should identify whether gateway filtering alone meets the requirement or whether API-level visibility is important enough to justify the higher service tier and additional tenant integration.
Hosted operations without appliance lifecycle
The Hosted model changes operational responsibility. There is no customer-owned FortiMail appliance to rack, power, replace or size for local compute resources, and no customer-provided VM infrastructure to maintain. This can simplify lifecycle planning for teams that prefer an operational-expenditure subscription. However, hosted infrastructure does not eliminate customer responsibilities. The organisation still needs to govern mail policy, domains, user administration, integrations, incident handling, quarantines, sender authentication and business processes. Buyers should compare this model with FortiMail Cloud SaaS as well: Hosted is a configurable Fortinet-hosted gateway service licensed per mailbox, while Cloud SaaS is a separate cloud-native offering licensed per user and designed for simplified cloud-mail protection.
Where the hosted model can make practical sense
Microsoft 365 organisations
Businesses can use gateway-style filtering around Exchange Online and evaluate the API Connector when internal-message scanning, mailbox visibility or post-delivery remediation is required. Connector design, accepted domains, sender authentication and tenant permissions should be documented before change.
Google Workspace environments
Hosted gateway protection can add a dedicated email-security layer for Gmail-based business mail. If API functions are selected, the customer should confirm supported integration, permissions and the relevant Premium with API Connector entitlement.
Exchange and hybrid mail
Organisations running on-premises Exchange or a coexistence design can use hosted filtering, but routing becomes more important. The project should map authoritative domains, relay paths, TLS, third-party senders and the cutover sequence.
Multi-site businesses
A central hosted email-security service can support organisations with offices across several locations without placing a mail-security appliance at each branch. Mail architecture and tenant design matter more than the number of physical sites.
Integration and operational considerations
A hosted gateway changes the path that business email takes. For inbound mail, DNS and mail-routing records may need to direct messages through the FortiMail Cloud service before the destination mail platform. Outbound filtering can require connectors or relay settings that route authorised messages through the service. These changes should be tested with representative users, application mail and external partners before broad enforcement.
Sender authentication deserves its own workstream. SPF, DKIM and DMARC records help receiving systems evaluate whether a sender is authorised and whether a message aligns with the visible From domain. A new gateway or relay path can affect those relationships. Inventory CRM systems, ticketing systems, payroll services, marketing platforms, printers, scanners, ERP applications and any other service that sends mail using company domains. Leaving one of these senders out of the design can create avoidable rejection or spoofing problems.
Operational ownership should also be explicit. Decide who reviews quarantines, handles false positives, manages allow and block policies, responds to suspected phishing, reviews reports and approves configuration changes. If FourTeck implementation or ongoing support is required, define which of these tasks are included in the quotation rather than assuming the product subscription covers all operational activity.
Buyer questions to resolve before requesting a quote
Fortinet publishes mailbox bands, so the declared active-mailbox count determines the commercial SKU range. Separate employees from actual licensed mailbox objects when preparing the number.
Premium adds controls such as cloud sandboxing, CDR, URL click protection and impersonation analysis. Select the tier from required controls rather than price alone.
If real-time or scheduled mailbox scanning and post-delivery clawback are important, confirm the Premium with API Connector offer and supported Microsoft or Google integration.
Groups with subsidiaries or several brands should list primary and alias domains. Current Gateway ordering guidance states up to 10 protected domains, so the exact domain structure should be validated.
Image analysis and email continuity are shown as add-ons. Include them only when they solve a defined requirement and confirm how they are licensed for the chosen tier.
Clarify whether the requirement is subscription supply only or includes DNS changes, mail connectors, policy setup, API integration, testing, documentation and handover.
Procurement checklist for FortiMail Cloud Hosted
✓ Confirm exact Hosted service tier: Gateway, Gateway Premium or Premium with API Connector.
✓ Record the number of active mailboxes and the expected growth during the subscription term.
✓ List primary protected domains, aliases and subsidiary domains.
✓ Identify Microsoft 365, Google Workspace, Exchange or hybrid mail architecture.
✓ Decide whether inbound-only or inbound-and-outbound filtering is required.
✓ Confirm whether sandboxing, CDR, click protection and impersonation analysis are required.
✓ Confirm whether Cloud Email API integration and post-delivery remediation are required.
✓ Review optional image analysis and email continuity requirements.
✓ Inventory third-party systems and applications that send email using company domains.
✓ Document DNS, SPF, DKIM, DMARC, TLS and connector responsibilities.
✓ Choose the requested subscription term and confirm current Fortinet SKU availability.
✓ Define whether FourTeck configuration, testing, migration or handover support is required.
How FourTeck can help turn a product name into a usable requirement
A request that says only “FortiMail Cloud Hosted” is not yet enough for an accurate subscription quotation because there are several mailbox bands and service tiers. FourTeck can help structure the requirement by confirming the mail platform, active-mailbox population, domains, desired controls, subscription term and implementation scope. This avoids treating a base Gateway SKU as though it includes Premium services or assuming that API-based scanning is automatically part of the hosted service.
For new deployments, the discussion can include gateway routing, connector planning, DNS and sender-authentication changes, cloud API prerequisites, quarantine workflow, policy design, testing and handover. For an existing FortiMail customer, FourTeck can review the current service reference, renewal term and whether a different Hosted tier is required as the organisation grows or changes its mail platform.
Related FourTeck resources include the business security product directory, technology services and implementation support, the Fortinet UAE portfolio, and FourTeck quotation assistance. If the project also includes network security, review the Fortinet firewall planning page to keep email and perimeter controls within a coordinated security architecture.
UAE availability and support guidance
FortiMail Cloud Hosted is a subscription service, so “availability” is different from hardware stock. A UAE order depends on the requested service tier, mailbox band, term, regional provisioning conditions and any optional services. Contact FourTeck to confirm the current SKU and commercial position for the exact requirement. If the customer also needs configuration or migration services, the project schedule should be agreed separately from subscription provisioning.
A useful UAE request includes the email platform, active mailbox count, domains, desired security tier, API integration requirement, subscription term and target onboarding window. If the existing environment uses complex relays, multiple tenants, hybrid Exchange or many third-party senders, share that context early so the proposed deployment scope reflects the real change effort. No fixed delivery, provisioning or installation date should be assumed until the final requirement is reviewed.
Dubai, Abu Dhabi, Sharjah and Ajman project coordination
Businesses in Dubai, Abu Dhabi, Sharjah and Ajman can use the same FortiMail Cloud Hosted service; the service itself is not a different product by emirate. Location becomes relevant when FourTeck is coordinating meetings, local project resources, change windows, customer stakeholders or related hardware and network work. A multi-site UAE business may have offices in several emirates while using one Microsoft 365 tenant or central mail architecture, so the email-security design is normally built around the tenant, domains, mail flow and administrative model rather than separate city installations. Share the main project location, any branches involved, preferred coordination method and whether remote or on-site services need to be considered in the quotation.
GCC Availability
FourTeck can assist organisations planning FortiMail Cloud Hosted requirements across GCC markets by reviewing mailbox quantities, service tiers, email platforms, subscription terms and implementation responsibilities before a quotation is prepared. For businesses operating in the United Arab Emirates, Saudi Arabia, Kuwait, Qatar, Bahrain or Oman, the commercial and technical process should begin with the exact destination organisation and mail environment rather than assuming one regional SKU or service condition applies everywhere. Product availability, licensing, provisioning schedules, service visits, optional implementation work and vendor lead times can vary by country, mailbox bracket and requirement. Buyers should provide the destination country, number of active mailboxes, protected domains, selected or desired Hosted tier, subscription term, mail platform and expected project window. FourTeck can then coordinate current options, configuration scope and regional procurement guidance without implying local stock, fixed provisioning times or country-specific certification that has not been confirmed.
Africa Availability
Organisations evaluating FortiMail Cloud Hosted for Africa can work with FourTeck to clarify the subscription, licensing and deployment requirements before committing to a regional procurement plan. Cloud email-security projects often depend less on physical shipment and more on service-region eligibility, mailbox volume, domain structure, subscription term, cloud-mail integration, customer access and implementation scope. Businesses in East Africa, including Kenya and Uganda, as well as organisations in other African regions, should share the destination country, active mailbox count, Microsoft 365, Google Workspace or Exchange environment, required security tier, desired API capabilities and target deployment period. Availability and fulfilment can vary according to vendor policy, licensing region, quantity, provisioning process and local project conditions. FourTeck can help review these dependencies, coordinate a current quotation and discuss configuration or support needs, but local inventory, customs outcomes, country-wide onsite coverage or guaranteed deployment dates should not be assumed unless specifically confirmed.
What buyers are really trying to work out before choosing FortiMail Cloud Hosted
Hosted versus SaaS is an architecture choice, not a naming detail
One of the most important comparisons is FortiMail Cloud Hosted versus FortiMail Cloud SaaS. Both are cloud-delivered Fortinet email-security options, but they are not interchangeable. Hosted is a Fortinet-operated FortiMail service that retains a secure-email-gateway orientation and is commercially described per mailbox per year. Cloud SaaS is a separate cloud-native offering licensed per user per year and designed around simplified protection for cloud email platforms. A company that wants a highly configurable gateway without managing infrastructure can find Hosted attractive. A company focused on cloud-native integration, simplified operations and the newer FortiMail Workspace Security approach may need to compare Cloud SaaS instead. The right answer depends on how email is routed, how much policy control the security team wants, which integrations are required and how procurement prefers to license users or mailboxes.
Mailbox count is a commercial input, but mail architecture determines the project
Fortinet publishes Hosted mailbox bands beginning at 25–100 and scaling through larger enterprise brackets. That makes mailbox count essential for pricing, but it does not tell the whole deployment story. Two organisations with 500 mailboxes can require very different designs. One may use a single Microsoft 365 tenant with two domains and simple outbound mail. The other may have several accepted domains, applications that relay mail, subsidiary brands, shared mailboxes, an Exchange hybrid environment and strict transport rules. The second environment needs more discovery and testing even though the mailbox quantity is identical. When preparing a quotation, include the mailbox count, but also describe mail platforms, domains, inbound and outbound paths, third-party senders and any migration in progress.
API integration matters when threats must be handled after delivery
Secure email gateways make decisions while messages pass through mail flow. Modern threat handling sometimes needs another layer because a message can be reclassified after delivery or an internally delivered message may not have passed through the same external gateway path. Fortinet’s Hosted ordering model provides API-based capabilities with the appropriate premium API connector offering. These include mailbox scanning and post-delivery clawback functions in supported environments. Buyers using Microsoft 365 or Google Workspace should therefore decide whether they only need gateway filtering or whether post-delivery visibility and remediation are part of the security objective. Choosing the API Connector also introduces tenant permission and integration planning that should be included in implementation scope.
Premium controls should be tied to actual risk scenarios
A procurement team may see Premium as simply the “better” option, but security teams should connect each advanced control to a business requirement. Cloud sandboxing can be important when unknown attachments need dynamic analysis. Content disarm and reconstruction can help organisations that want to remove risky active content from supported files. URL click protection addresses phishing techniques that rely on links rather than attachments. Impersonation analysis can be relevant for finance, executive and supplier-fraud scenarios. These controls create value when they map to a documented threat model and operating process. They also require administrators to monitor results and tune policy. A higher tier is not a replacement for defined incident response, user verification and identity security.
Why buyers compare it with Microsoft 365 native protection
Microsoft 365 includes its own email-security controls, so the question is usually whether a dedicated third-party layer adds the policy separation, threat analysis, reporting, integration or operational model the organisation wants. A useful comparison looks at actual licence levels, incident workflows, false-positive handling, post-delivery remediation, reporting and team skill—not a generic claim that one platform replaces another.
Why “price per mailbox” can be misleading without context
Online prices often represent one mailbox in a specific volume band and subscription term. A production quote is calculated from the declared mailbox quantity, selected tier and applicable term, and it may include optional services or professional work. Comparing a single web-listed mailbox price with a complete UAE project quote can therefore produce the wrong conclusion. Ask for the exact SKU, quantity basis and included services.
When Hosted may not be the best fit
If the organisation requires customer-owned infrastructure, highly specific local deployment control or a licensing model based on VM resources rather than mailboxes, an appliance or FortiMail VM may fit better. If the goal is the simplest cloud-native service for Microsoft 365 or Google Workspace with newer workspace-security integrations, FortiMail Cloud SaaS should also be evaluated. FourTeck can help compare the operational models before a final quote is requested.
Questions that usually appear during technical and commercial review
Can Hosted protect cloud email without replacing Microsoft 365 or Google Workspace?
Yes. FortiMail Cloud Hosted is an email-security layer, not a mailbox hosting replacement. It can be integrated with cloud email platforms through gateway mail flow, and the appropriate API Connector offer can add supported mailbox scanning and post-delivery actions. The project should document connectors, DNS, accepted domains, tenant permissions and routing responsibility before implementation.
How should shared mailboxes and service accounts be counted?
Fortinet bills Hosted based on declared active mailboxes and validates declared counts through its own methods. Because real environments contain shared mailboxes, applications and special-purpose accounts, do not assume employee headcount equals the licensed quantity. Prepare an inventory and ask FourTeck to confirm how the current Fortinet policy applies to the objects in your tenant.
Do all Hosted packages include sandboxing and impersonation protection?
No. Current ordering guidance separates the base Gateway service from Premium offerings. Cloud sandboxing, URL click protection, content disarm and reconstruction and impersonation analysis are listed with Premium. An accurate quotation should name the required tier so advanced controls are not assumed to be part of the base service.
What changes if the company has many sending applications?
The mail-flow design becomes more important. ERP systems, CRMs, scanners, alerting platforms and marketing services may send through different routes and use different authentication methods. Include them in the sender inventory so SPF, DKIM, DMARC, relay permissions and outbound filtering can be planned without breaking legitimate application mail.
Should the quotation include implementation work?
Include professional services when the customer expects FourTeck to perform or coordinate DNS changes, connectors, policy configuration, API integration, testing, documentation or migration. Subscription provisioning and project implementation are different scopes. Listing the expected responsibilities in the quotation makes handover and scheduling clearer for both parties.
What information produces the fastest accurate quote?
Send the mail platform, active mailbox count, protected domains, desired subscription term, required Hosted tier if known, whether API integration is needed, expected onboarding window and whether implementation support is required. For a renewal, include the existing service reference or SKU context through an appropriate business channel.
Related FourTeck options to evaluate
FortiMail appliances
For organisations that want a dedicated on-premises platform and direct control over the email-security infrastructure. Model sizing should consider message rate, services, storage and availability requirements.
FortiMail virtual machines
For private cloud, public cloud or virtualised data centres where the customer wants to operate FortiMail on supported infrastructure. VM size, domains, resources and licensing model need to be confirmed.
FortiMail Cloud SaaS
A separate cloud-native service for Microsoft 365 and Google Workspace environments. It uses per-user annual licensing and should be compared with Hosted when simplified cloud-native operations are the priority.
Email-security implementation support
For projects that need mail-flow planning, connector configuration, policy setup, testing, migration coordination or operational handover in addition to the subscription itself.
Why businesses contact FourTeck for this requirement
FortiMail Cloud Hosted is straightforward as a product concept but detailed as a purchase. A valid order must connect the mailbox count to the correct volume band, the security requirement to the correct service tier, and the mail platform to the correct integration design. FourTeck can help translate those decisions into a quotation-ready request instead of leaving the customer to infer an SKU from a broad product name.
The discussion can include mailbox sizing, domain structure, Hosted versus Cloud SaaS comparison, Premium feature requirements, Cloud API Connector needs, optional services, subscription term and compatibility with the existing mail architecture. Where implementation is required, FourTeck can also help scope configuration, mail routing, API integration, testing, migration planning and handover responsibilities.
This approach is especially useful when a customer is moving from an appliance or VM, migrating Exchange to Microsoft 365, adding another domain, consolidating subsidiaries, or reviewing an expiring FortiMail subscription. The objective is to make sure the commercial item matches the environment that will actually be protected.
Fortinet FortiMail Cloud Hosted FAQs
Is FortiMail Cloud Hosted the same as FortiMail Cloud SaaS?
No. FortiMail Cloud Hosted is a Fortinet-hosted, configurable secure email gateway service licensed per mailbox per year. FortiMail Cloud SaaS is a separate cloud-native offering licensed per user per year. Compare mail-flow design, required controls, administration model and integration needs before choosing.
How is FortiMail Cloud Hosted licensed?
Fortinet publishes Hosted subscriptions on a per-active-mailbox annual basis with volume bands. Current ordering guidance lists bands beginning at 25–100 mailboxes and increasing for larger organisations. The exact current SKU and term should be confirmed before ordering.
What is included in the base Gateway service?
Current Fortinet ordering guidance lists FortiGuard AntiVirus, AntiSpam, Virus Outbreak Prevention, hosted infrastructure, inbound and outbound filtering, LDAP integration, TLS delivery, message tracking and reporting among the base Gateway capabilities. Premium features should not be assumed to be included.
When should we choose Gateway Premium?
Choose Premium when the requirement includes advanced controls such as cloud sandboxing, URL click protection, content disarm and reconstruction, impersonation analysis or identity-based encryption. Confirm the current package because Fortinet can update bundles and names.
Can Hosted integrate with Microsoft 365 and Google Workspace?
Yes. Gateway mail-flow protection can be used with cloud email platforms, and the appropriate Premium with API Connector offering supports Cloud Email API integration for Microsoft 365 and Google Workspace. Current guidance also references on-premises Exchange integration. Tenant and configuration prerequisites apply.
Does the API Connector provide post-delivery threat removal?
Current Fortinet ordering guidance lists real-time and scheduled mailbox scanning plus post-delivery clawback of newly discovered email threats in the API-supported Hosted offerings. The exact entitlement and supported integration should be verified for the subscription being quoted.
How many domains can the service protect?
The current FortiMail ordering guide states that the Gateway service supports up to 10 protected domains and explains associated-domain handling for aliases. Organisations with complex multi-domain structures should confirm the current commercial and configuration limits for their selected tier.
Is implementation included with the subscription?
Do not assume it is. Subscription provisioning, configuration, DNS changes, connectors, migration, API integration, testing and documentation can be separate project scopes. Ask FourTeck to include the required implementation services in the quotation.
What should we provide for a UAE quotation?
Provide the active mailbox count, email platform, protected domains, desired Hosted tier or required controls, subscription term, API integration needs, optional services and implementation expectations. If it is a renewal, include the current subscription reference or SKU context.
Can FourTeck confirm current UAE availability and pricing?
Yes. FourTeck can confirm the current commercial position for the exact FortiMail Cloud Hosted SKU and mailbox band. Price and provisioning depend on the requested tier, quantity, subscription term, optional services and current vendor conditions.
Build the correct FortiMail Cloud Hosted subscription
Send FourTeck your active mailbox count, mail platform, protected domains, required security controls and preferred term. We can help identify the applicable Hosted tier, API requirement, optional services and implementation scope for a UAE quotation.
Reviews
There are no reviews yet.