FortiMail Cloud Email Security in Dubai, UAE
FortiMail Cloud gives organisations a Fortinet-hosted route to stronger email protection without requiring them to operate the underlying security appliance or virtual infrastructure. It can filter inbound and outbound mail, apply FortiGuard security services, and scale licensing according to declared active mailboxes. The exact protection set depends on whether the requirement is Cloud Gateway, Cloud Gateway Premium, or a Premium package with cloud API integration and optional advanced management.
Decide the service tier before the SKU
Mailbox quantity matters, but feature requirements matter just as much. Premium security, cloud mailbox scanning, post-delivery clawback, advanced management and additional services are not identical across every FortiMail Cloud package.
What is FortiMail Cloud and who should consider it?
FortiMail Cloud is Fortinet’s hosted email-security offering for organisations that want cloud-delivered filtering and security controls without deploying the FortiMail infrastructure themselves. It is mainly used to inspect and protect business email against spam, phishing, malware, malicious links, impersonation and other email-borne threats, with additional controls available in higher service tiers. Businesses using Microsoft 365, Google Workspace, Exchange and supported SMTP-based environments may consider it when they need a dedicated email-security layer, central policy control and reporting. Before proceeding, buyers should confirm active mailbox count, domain count, inbound and outbound mail-flow design, the required security tier, cloud API needs, subscription term, identity-directory integration, and any implementation or migration support.
What it does
FortiMail Cloud sits in the email-security path to inspect inbound and outbound messages, apply anti-spam and anti-malware controls, track messages and provide reporting. Premium service levels extend the protection set with functions such as content disarm and reconstruction, URL click protection, impersonation analysis, cloud sandboxing and identity-based encryption.
Where a Premium package includes cloud API support, the service can also scan supported cloud mailboxes and perform post-delivery clawback of newly discovered threats. Those capabilities should not be assumed in the base Gateway package.
Who it suits
The service may suit organisations that want dedicated email security while keeping infrastructure ownership and hosting outside their own data centre. It is relevant to lean IT teams, distributed businesses, organisations standardising on cloud productivity platforms, and enterprises that need tiered protection according to risk and mailbox scale.
It may be less suitable when a business specifically requires full control of a physical or virtual FortiMail instance, a custom on-premises architecture, or a feature that exists only in another FortiMail deployment model. FourTeck can help compare the hosted option with appliance, VM and other FortiMail services.
Business problems FortiMail Cloud can help address
Phishing and impersonation pressure
Email remains a practical route for attackers to imitate executives, suppliers and trusted brands. FortiMail combines reputation, content analysis and advanced detection methods, while impersonation-specific functions depend on the selected Premium tier.
Malicious files and URLs
Layered anti-malware and threat-intelligence services can examine messages before delivery. Premium packages can extend analysis with cloud sandboxing, URL click protection and content disarm and reconstruction.
Cloud mailbox remediation
For Microsoft 365 or Google Workspace environments, API-enabled Premium offerings can add mailbox scanning and post-delivery clawback. This is a licensing and configuration dependency rather than a universal FortiMail Cloud feature.
Operational overhead
A hosted service can reduce the need to size, deploy and maintain dedicated FortiMail infrastructure. Customers still need to define domains, mail routing, policies, identities and operational responsibilities correctly.
Core capability band
FortiMail Cloud fit matrix
| Requirement | Suitable when | Confirm before ordering |
|---|---|---|
| Basic hosted gateway filtering | You need inbound/outbound scanning with core antivirus, antispam and outbreak protection. | Mailbox bracket, protected domains and mail-routing design. |
| Advanced threat protection | You need CDR, URL click protection, impersonation analysis, cloud sandboxing or IBE. | Premium entitlement and any add-on services. |
| Microsoft 365 or Google mailbox scanning | You want supported API-level mailbox scanning and post-delivery clawback. | Premium with Cloud API connector/support and tenant prerequisites. |
| Multi-domain or advanced administration | You need more complex administrative separation, profiles or import workflows. | Advanced management licensing and exact domain requirements. |
| No customer-managed security infrastructure | You prefer a Fortinet-hosted service rather than an appliance or customer-operated VM. | Service responsibility, integration scope and operational handover. |
Verified service information
FortiMail Cloud is a subscription service rather than a fixed hardware appliance, so the most important “specifications” are the deployment model, licensing basis and tier-dependent capabilities. The table below separates confirmed service characteristics from items that must be scoped for the individual customer.
| Brand | Fortinet |
|---|---|
| Product | FortiMail Cloud |
| Product type | Hosted cloud email security |
| Deployment type | Fortinet-hosted cloud service |
| Licensing basis | Annual subscription, charged according to active mailbox range for Cloud Gateway offerings |
| Core Cloud Gateway security services | FortiGuard AntiVirus, AntiSpam and Virus Outbreak Prevention Service |
| Premium security additions | Includes capabilities such as FortiMail Cloud Sandbox, CDR, URL Click Protection, Impersonation Analysis and IBE; exact bundle should be confirmed |
| Cloud email API integration | Available in specific Premium options for supported Microsoft and Google environments |
| Post-delivery clawback | Available with cloud API-enabled Premium options |
| Inbound / outbound filtering | Supported |
| Customer LDAP integration | Supported in Cloud Gateway feature set; deployment prerequisites apply |
| Secure message delivery | TLS supported; identity-based encryption is Premium dependent |
| Message tracking and reporting | Supported |
| Protected domains | Up to 10 protected domains are specified for standard Cloud Gateway offerings in the current ordering guide; advanced/MSSP requirements differ |
| FortiCare / support | Support is included in current FortiMail solutions; exact service level and entitlement should be confirmed with the selected subscription |
| UAE price | Contact FourTeck for a current quotation based on mailbox range, tier and term |
| Availability | Contact FourTeck to confirm current UAE licensing availability, provisioning lead time and service scope |
Important licensing and scope dependencies
The words “FortiMail Cloud” describe more than one service configuration. Buyers should not assume that every capability found on a FortiMail feature list is included in the base Cloud Gateway subscription. The current Fortinet ordering model separates Cloud Gateway, Cloud Gateway Premium, and Premium options with cloud API integration. Advanced administration functions and some additional services can require separate entitlements or bundles.
Billing is tied to the customer-declared number of active mailboxes, with SKU selection based on the applicable mailbox range. Confirm whether all active accounts count toward licensing, how aliases and shared mailboxes should be treated, how many protected domains are required, and whether the planned environment needs API access to Microsoft 365 or Google Workspace. FourTeck can use that information to prepare the correct bill of materials instead of relying on a generic “FortiMail Cloud” line item.
A practical purchase and deployment journey
Inventory mailboxes and domains
Start with active mailbox count, protected domains, aliases, shared addresses and mail-flow direction. This sets the licensing bracket and reveals whether the standard domain allowance fits the environment.
Choose the protection tier
Map required controls to Gateway, Gateway Premium, or Premium with cloud API integration. Do not pay for an API-enabled tier if the deployment will not use mailbox scanning, and do not select base Gateway when the requirement includes Premium-only controls.
Design mail flow and identity
Confirm inbound and outbound routing, DNS changes, connectors, permitted senders, LDAP or directory integration, TLS requirements, quarantine workflows and any cloud-platform API prerequisites.
Quote subscription and services
Specify subscription term, mailbox band, tier, implementation scope, migration assistance, policy configuration and documentation requirements so the quotation reflects the full project rather than licensing alone.
Pilot, tune and hand over
After provisioning, test routing, quarantine handling, policy actions, legitimate bulk senders, outbound flows and reporting. Security filtering usually needs measured tuning to match the organisation’s mail patterns and risk tolerance.
Layered protection without customer-operated infrastructure
A central reason to consider FortiMail Cloud is architectural rather than purely feature based. A company can use dedicated FortiMail email-security controls while Fortinet hosts the underlying service infrastructure. That changes the operational burden: the customer still owns policy decisions, mail-flow planning, identity information, domain configuration, user communications and security governance, but it does not need to procure, rack or hypervisor-host a FortiMail appliance for the cloud-hosted deployment.
The core Gateway tier provides a sensible baseline for organisations that need hosted inbound and outbound filtering with antivirus, antispam, virus outbreak protection, message tracking, reporting and other gateway functions. The Premium tier is designed for organisations that need additional controls such as content disarm and reconstruction, URL click protection, impersonation analysis, cloud sandboxing and identity-based encryption. These distinctions matter because an email-security project can fail procurement review if the buyer compares only the brand name and mailbox count while overlooking the entitlement required for the actual use case.
FourTeck can help translate a security requirement into a subscription tier by asking what the organisation needs to stop, detect, inspect, encrypt, trace and remediate. That discussion is more useful than beginning with a SKU. Once the required controls are agreed, the appropriate mailbox range and subscription term can be matched to the service.
Microsoft 365 and Google Workspace: gateway and API decisions
Cloud productivity suites already provide native email-security controls, but many organisations add a dedicated security layer when they want broader policy options, specialised threat detection, central visibility or a consistent control model. FortiMail supports gateway-based protection for cloud email platforms, and selected FortiMail Cloud Premium options add API-level integration for Microsoft 365 and Google environments.
Gateway protection and API integration solve different parts of the problem. Gateway filtering inspects mail as it flows through the secure email gateway. API integration can inspect supported cloud mailboxes and, in the appropriate FortiMail Cloud tier, enable real-time or scheduled mailbox scanning and post-delivery clawback when a message is later determined to be malicious. A buyer who needs only perimeter-style mail-flow control may not need the same subscription as a buyer who wants post-delivery action inside cloud mailboxes.
The technical preparation also differs. Microsoft 365 deployments typically require mail connectors, routing rules, DNS and domain validation decisions, while API-enabled functions require suitable cloud permissions and tenant integration. Google Workspace deployments similarly require routing and gateway configuration, with API-enabled features depending on the selected service and tenant prerequisites. The exact implementation should be planned before changing production MX records or mail connectors.
For a quotation, tell FourTeck which cloud email platform is used, whether inbound and outbound mail must be filtered, whether post-delivery remediation is required, how many domains exist, and whether the customer wants assistance with connector configuration, DNS planning, testing and policy tuning.
Operational visibility, reporting and response workflows
Email security is not only about blocking messages. Operations teams need to understand why a message was allowed, quarantined or rejected; identify affected recipients; investigate suspicious senders; and provide evidence when users report possible phishing. FortiMail Cloud supports message tracking and reporting so administrators can work from an email-security view rather than relying solely on user screenshots or mailbox searches.
The value of these functions depends on how the organisation structures access and process. Decide who will review quarantine, who can release a message, how false positives are escalated, which security team receives alerts, how reports are used, and whether the organisation needs central administration across multiple domains. Some advanced administration functions require additional licensing, so a complex managed-service or group-company environment should be discussed early.
Integration with the wider Fortinet Security Fabric can also be relevant where an organisation already uses FortiGate, FortiSandbox, FortiSIEM or FortiSOAR. Fortinet documents FortiMail integration with these platforms to improve visibility and support response workflows. That does not mean every integration is automatically configured or licensed. Buyers should identify existing Fortinet components and desired workflow outcomes so FourTeck can include compatible integration planning in the scope.
Ideal business environments and use cases
Microsoft 365 organisations
Businesses wanting a dedicated secure email gateway plus the option of cloud API scanning and clawback in eligible Premium tiers.
Google Workspace environments
Organisations that want layered filtering and, where selected, API-enabled mailbox inspection while retaining Google as the core email platform.
Hybrid mail architectures
Enterprises with cloud and on-premises email components that need careful routing, domain and policy design rather than a one-size-fits-all deployment.
Lean security teams
Teams that prefer a Fortinet-hosted service and want to avoid managing dedicated FortiMail hardware while retaining email-security administration.
Multi-domain businesses
Companies with several business units or brands, provided domain count and advanced administration needs are confirmed before licensing.
Compliance-conscious teams
Organisations that need stronger mail inspection, reporting, secure delivery or data-control workflows, while understanding that specific compliance outcomes depend on policy and broader governance.
Integration and operational considerations before go-live
A FortiMail Cloud subscription is only one part of a successful deployment. The service must be connected to the organisation’s actual mail architecture. That usually means identifying every inbound and outbound route, business application that sends mail, relay requirement, domain, mail server, accepted sender, and authentication dependency. Systems such as CRM platforms, ERP applications, multifunction printers, alerting tools and line-of-business applications can be overlooked during a simple email migration and then fail when security controls become stricter.
DNS planning is especially important. MX records determine inbound delivery, while SPF, DKIM and DMARC influence sender authentication and domain reputation. Changing a gateway can affect how these controls should be configured, particularly for outbound routing and third-party senders. The project plan should identify the authoritative DNS owner, change window, rollback method and validation steps. It should also define how encrypted delivery is handled, whether TLS is mandatory for selected partners, and how quarantine notifications will reach users.
Directory integration can improve recipient validation and policy targeting, but the customer should confirm whether LDAP or another supported identity source is available and reachable under the chosen architecture. If cloud API functions are required, tenant permissions and administrator access must be prepared. The organisation should also document who owns policy tuning after go-live, because acceptable email behaviour differs by industry and by business role.
FourTeck can help include these dependencies in the quotation and implementation discussion so the project is not reduced to “activate a license and change the MX record.”
Buyer questions to resolve before ordering
The mailbox count determines the licensing band and should be based on the customer’s actual declared active mailbox population.
List requirements such as sandboxing, CDR, impersonation protection, encryption and post-delivery remediation before selecting Gateway or Premium.
Microsoft 365 and Google Workspace buyers should decide whether gateway filtering alone is sufficient or API-based mailbox scanning is part of the requirement.
Standard Cloud Gateway offerings specify support for up to ten protected domains, so larger or more complex domain structures should be reviewed.
Record the mail platform, DNS ownership, directory service, applications that relay email, existing Fortinet security products and any SIEM or SOAR workflows.
Separate licensing from design, implementation, migration, configuration, policy tuning, documentation, training and post-deployment support expectations.
Procurement checklist for a cleaner quotation
How FourTeck can assist with sizing and configuration
FourTeck can help turn a broad email-security requirement into a quotation that identifies the correct FortiMail Cloud tier, mailbox bracket, subscription term and implementation scope. This is particularly useful when a customer says “we need FortiMail Cloud for Microsoft 365” but has not yet decided whether it needs gateway filtering only, Premium threat controls, cloud mailbox scanning, post-delivery remediation or advanced administration.
The review can include current email platform, active mailbox count, domains, outbound applications, inbound mail sources, DNS ownership, identity integration, quarantine workflow, reporting needs, encryption requirements and existing Fortinet products. Based on the information provided, FourTeck can coordinate a bill of materials and clarify what is subscription dependent versus part of the deployment service.
For broader infrastructure planning, buyers can review FourTeck technology products, explore configuration and security services, or contact FourTeck with the mailbox count and deployment details.
UAE availability and support guidance
Contact FourTeck to confirm current UAE availability for the required FortiMail Cloud subscription, mailbox tier and service option. Availability can depend on the selected bundle, subscription term, quantity, account details, vendor provisioning process and regional licensing conditions. Because FortiMail Cloud is a hosted subscription rather than a stocked appliance, the key timing questions are normally licensing confirmation, account provisioning, tenant readiness and implementation planning.
If configuration assistance is required, include it in the quotation request. FourTeck can discuss mail-flow planning, Microsoft 365 or Google Workspace integration, DNS changes, policy configuration, testing and handover as separate scope items. Buyers should also confirm the required support path and operational responsibilities after go-live. For a UAE quotation, share the active mailbox count, required tier, subscription term, domains and preferred deployment timeline through the FourTeck UAE contact channel.
Dubai, Abu Dhabi, Sharjah and Ajman coverage
Businesses in Dubai, Abu Dhabi, Sharjah and Ajman can contact FourTeck for FortiMail Cloud requirement review, licensing guidance, quotation coordination and project planning. For cloud email-security projects, physical location is only one part of the requirement: the email tenant, domain structure, mailbox population, DNS ownership and integration scope are usually more important to service design. Where installation or configuration assistance is requested, the quotation should define whether work is remote, on-site, hybrid, migration related or limited to advisory support. Current subscription availability, provisioning time and service scheduling should be confirmed for each project rather than assumed from another customer or previous order.
GCC Availability
FourTeck can assist organisations planning FortiMail Cloud projects across the GCC by reviewing mailbox requirements, service tiers, licensing terms and integration scope before a quotation is prepared. Businesses in the United Arab Emirates, Saudi Arabia, Kuwait, Qatar, Bahrain and Oman may have different procurement processes, tenant locations, billing entities and implementation expectations, so the exact destination and contracting requirement should be identified early. For Microsoft 365 and Google Workspace environments, the technical design should also confirm whether the project needs gateway filtering only or a Premium option with cloud API integration.
Product availability, licensing, delivery of subscription entitlements, service visits, project scope and vendor lead times can vary by country, mailbox quantity, subscription term and selected bundle. Buyers should provide the destination country, active mailbox count, protected domains, required FortiMail Cloud tier, desired contract term and expected deployment date. FourTeck can then coordinate licensing and project guidance without assuming local stock, fixed lead time or guaranteed on-site availability. For Kuwait-specific technology enquiries, the FourTeck Kuwait resource can also be used as a regional point of reference.
Africa Availability
Organisations evaluating FortiMail Cloud in Africa can contact FourTeck for product and license selection, mailbox sizing, subscription planning, compatibility review and deployment-scope guidance. Cloud email-security projects in East Africa, West Africa, Southern Africa and Central Africa can differ in connectivity design, tenant ownership, regulatory requirements, local IT resources and procurement processes. The destination country and customer environment should therefore be identified before assuming that a licensing option, service plan or implementation model used elsewhere will apply unchanged.
Availability and fulfilment may depend on the destination, mailbox quantity, license region, chosen FortiMail Cloud tier, vendor provisioning lead time, local project conditions and any requested installation or support services. Buyers should share the destination country, exact email platform, active mailbox count, protected domains, required security functions and intended deployment schedule. FourTeck can help coordinate the relevant commercial and technical questions. Businesses can also review FourTeck Africa technology support, including regional resources for Kenya and Uganda, while confirming country-specific fulfilment before ordering.
Related FourTeck options and complementary services
FortiMail appliance or VM
Consider customer-operated FortiMail when infrastructure control, deployment architecture or custom operational requirements make hosted Cloud less suitable.
FortiGate security
FortiGate can complement email security as part of a broader Fortinet environment, but firewall and email-security controls solve different parts of the threat surface.
Email-security implementation support
Include mail-flow, DNS, connector, policy, testing and handover tasks in the scope when internal teams do not want to manage the deployment alone.
Subscription renewal planning
Review active mailbox counts, tier suitability and feature use before renewal instead of automatically repeating the previous subscription.
Why businesses contact FourTeck for FortiMail Cloud
Email-security procurement often looks simple until the buyer reaches the licensing and integration details. FourTeck can help clarify whether the requirement is hosted gateway filtering, a Premium security tier, cloud API integration, advanced management, or a broader Fortinet architecture. That requirement clarification can reduce the risk of ordering a mailbox SKU that does not include the control the business actually expects.
Assistance can also cover bill-of-material preparation, compatibility questions, implementation planning, configuration scope, migration coordination, renewal review and support handover. These are practical project services rather than claims that one subscription automatically fits every business. Buyers can learn more about FourTeck’s business technology focus or send the active mailbox count and email-platform details directly through the contact page.
What buyers are usually trying to solve before choosing FortiMail Cloud
Most organisations do not start an email-security project because they want another dashboard. They start because users are receiving convincing phishing messages, executives are being impersonated, suppliers are being spoofed, malicious links are bypassing basic controls, or security teams need better evidence when an incident is reported. FortiMail Cloud should therefore be evaluated against the organisation’s actual email attack patterns and operational gaps rather than treated as a generic add-on to Microsoft 365 or Google Workspace.
Do we need a secure email gateway if we already use Microsoft 365?
That depends on the control gap you are trying to close. Microsoft 365 includes native security, but some organisations want a dedicated email-security platform for additional filtering layers, specialised threat analysis, policy separation, reporting or integration with a broader Fortinet security environment. The right question is not whether the cloud platform has security; it is whether the current security controls meet the organisation’s risk, operational and investigation needs.
What is the difference between FortiMail Cloud Gateway and Premium?
The base Gateway service includes core FortiGuard antivirus, antispam and outbreak-protection services plus gateway functions such as inbound/outbound filtering, tracking and reporting. Premium adds a broader threat-control set, including cloud sandboxing and functions such as CDR, URL click protection, impersonation analysis and identity-based encryption. Exact ordering terms can evolve, so quote against the current Fortinet ordering guide.
Another frequent question is whether FortiMail Cloud can “scan inside” Microsoft 365 or Google Workspace rather than only filtering messages in transit. Selected Premium packages with cloud API integration are designed for this use case. They can add real-time and scheduled mailbox scanning and post-delivery clawback for supported cloud email environments. A buyer who expects this functionality should explicitly request the API-enabled option; purchasing a base gateway SKU based only on mailbox count may not meet the requirement.
Pricing questions are also common, but a useful business quotation needs more than a per-mailbox number. FortiMail Cloud licensing is tiered by mailbox population, and subscription prices vary according to mailbox bracket, protection tier, subscription length and reseller terms. Public prices found online may represent different regions, renewal SKUs, mailbox bands or older ordering structures. For a UAE procurement decision, the buyer should first fix the active mailbox count and required feature set, then request a current local quotation rather than multiplying a random online unit price.
Fortinet’s ordering guide states that billing is based on customer-declared active mailboxes and the relevant mailbox range. A clean count avoids two problems: underestimating licensing and comparing a low-volume per-mailbox price with a high-volume rate that does not apply to your organisation. Include shared and special-purpose mailboxes in the licensing discussion rather than assuming they are excluded.
Deployment questions matter just as much as licensing. In a Microsoft 365 gateway design, connectors and mail routing must be planned so inbound and outbound messages pass through the intended security service without creating loops or bypass paths. In Google Workspace, routing and gateway settings similarly need to be aligned with the chosen protection model. DNS records, sender-authentication controls, outbound applications and third-party services should be documented before cutover. A marketing platform or ERP system that sends mail directly to the internet can bypass the new gateway unless its route is deliberately included.
Security teams also ask how FortiMail Cloud helps with false positives. No email filter should be deployed with the assumption that tuning is unnecessary. Organisations should identify trusted bulk senders, newsletters, automated notification systems and business partners that generate unusual mail patterns. Quarantine policy, release permissions, reporting and escalation paths should be tested before the system is treated as business-as-usual. The goal is to improve security while preserving legitimate business communication.
Finally, buyers should distinguish FortiMail Cloud Hosted from other FortiMail delivery models. Fortinet currently offers appliances, virtual machines, FortiMail Cloud Hosted and FortiMail Cloud SaaS/Workspace-related services. They share a FortiMail security heritage, but deployment responsibilities, licensing and feature sets are not identical. If the requirement simply says “FortiMail Cloud,” FourTeck can help confirm which current service is intended before the quotation is finalised.
Questions that shape the right FortiMail Cloud design
Should we choose gateway-only protection or API-enabled protection?
Choose based on the response you need after mail reaches the cloud mailbox. Gateway filtering focuses on mail flow before or during delivery. API-enabled Premium options add mailbox scanning and post-delivery clawback for supported Microsoft 365 and Google environments. If the security team wants to remove a newly identified threat from mailboxes after delivery, call that out explicitly in the requirement.
What mailbox count should be used for licensing?
Use the customer’s declared active mailbox count as the starting point, then validate special mailbox types with the current ordering rules. Do not estimate from employee headcount alone because shared, functional and application-related addresses can complicate the count. FourTeck can prepare the quote once the licensing population is understood.
Can FortiMail Cloud protect outbound email too?
Yes, the hosted Cloud Gateway feature set includes inbound and outbound filtering. The useful planning question is which outbound sources must be routed through it. User mail may flow through Microsoft 365 or Google Workspace, while business applications, scanners or transactional systems may use different SMTP paths that need separate treatment.
Does every subscription include sandboxing and impersonation analysis?
No. Current ordering information separates base Gateway from Gateway Premium. Cloud sandboxing, impersonation analysis, URL click protection, CDR and other advanced controls are associated with Premium offerings. The quotation should state the selected tier so the buyer can verify that the expected controls are included.
What should we prepare before implementation?
Prepare the mail-domain list, current MX records, inbound and outbound routes, connector details, DNS access, directory information, administrative accounts, change window, test accounts and rollback plan. For cloud API integration, suitable tenant permissions must also be available. This preparation reduces avoidable cutover delays.
How should we compare FortiMail Cloud with an appliance or VM?
Compare operational ownership first. Cloud Hosted places service infrastructure with Fortinet, while appliance and VM deployments give the customer more direct control of the FortiMail instance. Then compare licensing, required features, integration needs, data-centre strategy, administrative responsibility and the organisation’s ability to operate the platform.
Frequently asked questions
Is FortiMail Cloud a hardware appliance?
No. FortiMail Cloud Hosted is a Fortinet-hosted email-security service. Fortinet also offers FortiMail hardware appliances and virtual machines for organisations that prefer customer-operated deployment models.
How is FortiMail Cloud licensed?
Current FortiMail Cloud Gateway ordering is subscription based and uses customer-declared active mailbox counts, with SKUs selected according to mailbox ranges. The exact tier and term must also be specified.
What is included in the base Cloud Gateway tier?
The current ordering guide lists core FortiGuard AntiVirus, AntiSpam and Virus Outbreak Prevention services, together with gateway functions such as inbound/outbound filtering, TLS delivery, message tracking and reporting.
What does Gateway Premium add?
Premium offerings add a broader security set that includes cloud sandboxing and features such as content disarm and reconstruction, URL click protection, impersonation analysis and identity-based encryption. Confirm the current bundle before ordering.
Can FortiMail Cloud integrate with Microsoft 365?
Yes. Fortinet supports gateway integration with Microsoft 365, and selected Premium options provide cloud API integration for mailbox scanning and post-delivery actions. Connector, DNS and tenant configuration are required.
Can it work with Google Workspace?
Yes. Fortinet publishes FortiMail Cloud integration guidance for Google Workspace. The implementation and available mailbox-level functions depend on the selected FortiMail Cloud tier and integration model.
Does FortiMail Cloud include post-delivery clawback?
Post-delivery clawback is associated with Premium cloud API-enabled options rather than the base Gateway tier. Buyers should explicitly request this capability when it is part of the security requirement.
What information does FourTeck need for a quote?
Provide active mailbox count, protected domains, current email platform, required security tier, API-integration requirement, subscription term and any configuration, migration or testing scope.
Is FortiMail Cloud available in Dubai and the UAE?
FourTeck can assist UAE buyers with licensing and quotation coordination. Current availability, provisioning lead time, subscription terms and service scheduling should be confirmed for the exact mailbox range and bundle.
Build the FortiMail Cloud quote around your real mailbox environment
A useful quotation should identify the FortiMail Cloud tier, active mailbox range, protected domains, subscription term, cloud API requirement and any implementation services. Send FourTeck your current email platform and mailbox count, and the team can help structure the licensing and deployment discussion for Dubai or another UAE location without assuming stock, price or project timing.