Streamline Your Enterprise with Omnissa Connect and Microsoft Entra ID

May 21, 2026 fabio1975Azure, Azure Active Directory, cloud, EntraID, Federation, Horizon, OMNISSA, Omnissa ConnectLeave a comment

A guide to enterprise federation, single sign-on, and modern identity management

What is Omnissa Connect?

Omnissa Connect is a centralized platform service that provides IT administrators and users with a single sign-on (SSO) gateway to access and manage all Omnissa services, such as Workspace ONE and Horizon. It streamlines workflows by unifying access, identity management, and service onboarding into one intuitive interface.

Key features of Omnissa Connect include:

•Unified Identity: Single sign-on capabilities and seamless integration with third-party identity providers like Microsoft Entra ID and Okta through the Omnissa Identity Service

•Centralized Administration: IT owners can securely assign roles, set multi-factor authentication (MFA) policies, and manage OAuth applications or API tokens across the entire Omnissa ecosystem

•Subscription Management: Visibility into all Omnissa service subscriptions from a single location

What is Microsoft Entra ID?

Microsoft Entra ID (formerly Azure Active Directory) is Microsoft’s cloud-based identity and access management service. It’s the foundation that millions of organizations use to manage employee identities, secure access to applications, and protect their digital assets.

Entra ID is likely already at the heart of your organization if you use:

•Microsoft 365 (Office 365, Teams, SharePoint)

•Azure cloud services

•Dynamics 365 or other enterprise applications

•Single sign-on (SSO) solutions for SaaS applications

Why Integrate Omnissa Connect with Microsoft Entra ID?

Connecting Omnissa Connect with Microsoft Entra ID through enterprise federation creates a powerful identity ecosystem. Here’s what you gain:

Single Sign-On (SSO)

Your users log in once with their corporate credentials and automatically gain access to Omnissa Connect—no separate usernames or passwords to remember.

Automatic User Provisioning

When you add or remove users in Entra ID, they’re automatically synced to Omnissa Connect. No manual account creation, no forgotten deprovisioning, no stale user accounts cluttering your systems.

Centralized Security

Manage all user access, permissions, and security policies from one central location. Apply multi-factor authentication (MFA), enforce password policies, and monitor access across your entire organization from Entra ID.

Reduced IT Overhead

Your IT team spends less time managing separate identity systems, resetting passwords, and troubleshooting access issues. Everything is automated and synchronized.

Improved Compliance

Maintain detailed audit logs of who accessed what and when. Meet regulatory requirements for access control and identity management with confidence.

A Real-World Example

Before Federation:

Sarah joins your company. The IT team manually creates accounts in Omnissa Connect, Microsoft 365, and four other systems. Sarah has to memorize 5 different passwords. When Sarah leaves three years later, the team forgets to deactivate her Omnissa Connect account, leaving a security gap.

After Federation:

Sarah’s first day: HR adds her to Entra ID. Omnissa Connect automatically creates her account and grants the right permissions. She logs in with her corporate email and password—the same one she uses for everything else. On her last day: HR removes her from Entra ID. Within seconds, Omnissa Connect and all other connected systems automatically deactivate her access. No manual steps. No forgotten accounts. No security gaps.

Is This Right for Your Organization?

Enterprise federation between Omnissa Connect and Entra ID is ideal if your organization:

•Already uses Microsoft Entra ID or Azure Active Directory

•Wants to simplify identity management and reduce IT burden

•Has multiple employees and wants to automate user provisioning

•Needs strong security controls and audit capabilities

•Is undergoing digital transformation and standardizing on cloud-based identity solutions

What’s Involved?

Configuring enterprise federation requires several steps—from verifying your domain to setting up the connection between systems to testing everything works smoothly. The process typically involves:

•Domain verification to prove your organization owns the domain

•Creating and configuring an Enterprise Application in Microsoft Entra ID

•Setting up authentication protocols and user attribute mapping

•Testing the setup before activating federation for all users

•Notifying users and helping them transition to the new authentication method

The Complete Step-by-Step Guide

While this overview covers the benefits and concepts, implementing enterprise federation involves detailed technical configuration. The complete guide is a comprehensive document with in-depth instructions, detailed screenshots, and step-by-step walkthroughs for both Omnissa Connect and Microsoft Entra ID configuration. Due to its length and technical depth, I share it directly with clients and organizations ready to implement the solution.

The complete guide includes:

•Detailed screenshots and instructions for each configuration step

•Exact fields to fill in on both Omnissa Connect and Entra ID

Ready to streamline your organization’s identity management?

If your organization is ready to implement enterprise federation between Omnissa Connect and Microsoft Entra ID, I’m here to help. Whether you need guidance on setup, troubleshooting during configuration, or best practices for managing the transition, I can provide a complete, step-by-step implementation guide tailored to your needs.

Get in touch to request the full technical guide and start your journey toward simplified, centralized identity management.

📧 Contact me for the complete implementation guide

Let’s simplify your organization’s identity and access management together.

Horizon Cloud Service Next Gen Apis – Chapter 2

February 27, 2026February 27, 2026 fabio1975cloud, Cloud Horizon Omnissa, Horizon Cloud Service, Next Gen, Powershell, RestAPI, Syslog, UAG, Unified Access GatewayLeave a comment

Immagine che contiene testo, Neon, Segnali luminosi, Insegna al neon Il contenuto generato dall'IA potrebbe non essere corretto.

Set Syslog settings across UAG deployments

In this second article on working with APIs in Horizon Cloud Services, we will focus on a practical, security-relevant use case: configuring Syslog on Unified Access Gateways (UAGs) deployed through Horizon Cloud.

Whether you are running Horizon Cloud Service on Microsoft Azure or Horizon Cloud Service on vSphere, centralized logging is a fundamental component of any secure and well-governed environment. Proper Syslog configuration ensures that security events, authentication logs, and operational data generated by UAG appliances are forwarded to your SIEM or log management platform for monitoring, auditing, and incident response.

Instead of performing manual configuration tasks, we will explore how to leverage Horizon Cloud APIs to automate and standardise Syslog settings across UAG deployments, improving consistency, scalability, and operational efficiency.

Now when can explain the API we need to use and how to apply the syslog configuration on UAG (In this case, I used an HCS on vSphere, the new solution where we don’t deploy the Connection Server, but we use the HCS control panel to configure Pools, Entitlements and other…)

The first step is always the authentication process; I explained how to create the API token in my previous post (Horizon Cloud Service Next Gen Apis – Chapter 1), and now I won’t explain it again.

Let’s go…..

How to show UAG information

This command displays the UAG’s information

Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v2/uag-deployments Method Get -Headers $Header

We have two UAG deployments connected to HCS, and the output displays two deployment ids:

The UAG id for HCS on vSphere is the second id.

Now I need to recover only the UAG IDs and OrgIDs

Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v2/uag-deployments -Method Get -Headers $Header | Select-Object -ExpandProperty content | Select-Object id,OrgId

The UAG id that I need to use for identifying the deployment for HCS on vSphere is:

6994998bcb2a7086afaddf1c

I will use this ID to associate the syslog configuration with the UAG server.

How to set the correct parameters for Syslog configuration

We need to create a Body value like this:

$Body = @{
  orgId  = "8a4931b3-e6ac-44bf-9d25-723f4119e46f"
  projectId = "Pollaio-Project"
  name = "Pollaio-Configuration2"
  syslogEventCategory = "ALL_EVENTS"
  syslogServerProtocolSettingsCreateTO = @{
    sourceToSyslogServerProtocol = "TCP"
  }
  syslogFormat = "TEXT"
  syslogURI = "192.168.111.223:514"
  includeSystemMessages = $true
  sources = @(
    @{
      type = "UAG"
      id   = "6994998bcb2a7086afaddf1c"
    }
  )
}

Where:

Value	Description	Accept value
OrgID	It is the OrgId that we recovered with the previous command	String
ProjectId	ID of theCSP project that owns this data	String
Name	User defined name of the syslog server configuration	String
SyslogEventCategory	Events sent from the UAG appliance to the syslog server	[ ALL_EVENTS, AUDIT_EVENTS ]
sourceToSyslogServerProtocol	The protocol used to send data from the UAG appliance to the syslog server	[ UDP, TCP, TLS, MQTT ]
syslogFormat		[ JSON_TITAN, TEXT ]
syslogURI	Syslog server URI	String
includeSystemMessages	If true, system messages are sent to the syslog server	[ $True]
sources	List of sources associated with the syslog server: Type = Source for the syslog server. For es: UAG Id = Id of the source associated with the syslog server (The Id value that we recovered with the previous command

How to set the configuration for UAG

$Body = @{
  orgId  = "8a4931b3-e6ac-44bf-9d25-723f4119e46f"
  projectId = "Pollaio-Project"
  name = "Pollaio-Configuration2"
  syslogEventCategory = "ALL_EVENTS"
  syslogServerProtocolSettingsCreateTO = @{
    sourceToSyslogServerProtocol = "TCP"
  }
  syslogFormat = "TEXT"
  syslogURI = "192.168.111.223:514"
  includeSystemMessages = $true
  sources = @(
    @{
      type = "UAG"
      id   = "6994998bcb2a7086afaddf1c"
    }
  )
}

#Convert Body to JSON
$JsonBody = $Body | ConvertTo-Json -Depth 5
#Send POST request to create Syslog Server UAG configuration
Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v1/syslog-server -Method Post -Headers $Header -Body $JsonBody

HOW to check SYSLOG Configuration on UAG deployment

Invoke-RestMethod -Uri https://cloud-sg.horizon.omnissa.com/admin/v1/syslog-server -Method Get -Headers $Header

The command output is like this:

Now I can see in my SYSLOG server the UAG Log

Horizon Edge Gateway Appliance – URL Checker

January 14, 2025January 14, 2025 fabio1975cloud, Horizon, Horizon Cloud Service - next-gen Edge Subnet URL Checker tool, Horizon Edge Gateway appliance, Omnissa Horizon Cloud ServiceLeave a comment

Horizon Edge Gateway Appliance is required to entitle your environment to Horizon subscription licenses, services and management features hosted in the Horizon Control Plane Services. To enable subscription license entitlement, Horizon Edge Gateway Appliance must be deployed in each Horizon Pod.

The Horizon Edge Gateway Appliance is deployed as a virtual appliance from vSphere® Web Client and paired to one of the Connection Servers in the pod. As part of the pairing process, the Horizon Edge Gateway Appliance virtual appliance connects the Connection Server to the Horizon Cloud Service to manage the subscription license. With a subscription license for Horizon, you do not need to retrieve or manually enter a license key for Horizon product activation.

One of the first checks to do before deploying the Horizon Edge Gateway Appliance is to verify the correct communication with the Omnissa cloud services to which it must connect.

To perform this operation there is a specific tool that “Horizon Cloud Service – next-gen Edge Subnet URL Checker tool”, it can also be used to perform post-installation checks when there are communication problems like this:

A screenshot of a computer error

Description automatically generated

We can download the tool from this link:

Utilities | Omnissa

Select the correct tool and download the file zip:

We will copy the file on windows os locate it on the same network subnet where we will locate the Horizon Edge Gateway Appliance

We will extract the compressed file:

A screenshot of a computer

Description automatically generated

We will need lunch the file EXE to start the test

A screenshot of a computer error

Description automatically generated

At the end of the execution of the test, the tool will create a folder (c:\WMwareUrlChekerOutput)

A screenshot of a computer

Description automatically generated

Where we will find the tool output, a file for a region

A screenshot of a computer

Description automatically generated

In my case, I checked the EMEA file (EU) and I saw that it is all OK (all URLs are Reachable).

A screen shot of a computer

Description automatically generated

EUC, un futuro luminoso per Horizon

May 9, 2024May 9, 2024 fabio19752024, App Volumes, Broadcom, cloud, Dem, EUC, Horizon, Horizon 8, OMNISSA, VDI, vmwareLeave a comment

In questi giorni c’è molto fermento nel mondo dell’EUC (‘End-User Computing) in merito alla comparsa sul mercato di un nuovo nome.

Ma partiamo con ordine, nel lontano 2008 mi avvicino al modo delle VDI (Virtual Desktop Infrastructure) inizialmente con l’automatizzazione di aule corsi, grazie a VMware e al suo prodotto che allora era stato appena rinominato in Horizon View (se non sbaglio precedentemente si chiama VMware VDM….. ancora oggi, nelle installazioni dei Connection Server, troviamo una cartella VDM sotto c:\ProgramData).

A diagram of a timeline

Description automatically generated with medium confidence

Col tempo le soluzione VDI di VMware sono evolute in maniera importante con l’aggiunta prima della tecnologia linked clones e poi con le instant clone (tecnologie che permettono di semplificare notevolmente la vita dell’amministratore delle postazioni di lavoro).

Abbiamo visto l’affiancare a Horizon soluzioni che permettono di sfruttare al meglio le VDI come App Volumes, DEM (Dynamic Environment Manager), Workspace One ecc.…

Poi dall’on-premise è stato portato anche sul Cloud con soluzione come Horizon Cloud on Microsoft Azure.

Anche per la mia carriera lavorativa il mondo delle VDI ha lasciato un solco importante dal 2021 sono vEXPERT (Con specificità nel mondo EUC) e dal 2024 sono EUCExpert e collaboro con VMware/Broadcom nel deploy.

Mi direte ok sono cose che ormai conosciamo ma quindi che cosa è successo??

Bene, sappiamo tutti che VMware è stata acquisita da Broadcom e una delle prime dichiarazioni della nuova proprietà è stata quella di non volere investire sull mondo EUC.

Ma quindi che succede?

Tutto i prodotti EUC di VMware sono riconosciuti tra i leader del mercato dei prodotti VDI e Desktop as a Service sono stati comprati da KKR (Fondo Americano nato nel 1977) per cui nasce Omnissa

Nata con persone VMware per garantire la stessa qualità e lo stesso sviluppo in innovazione che è stato garantito in questi anni.

In cui continua o parte una nuova vita (scegliete voi) per tutti i prodotti EUC che molti noi conosciamo e apprezziamo (Horizon ecc…)

Ne vedremo sicuramente delle belle e ci aspetta un futuro luminoso!

VMware Skyline Advisor

October 16, 2021October 16, 2021 fabio1975cloud, Skyline, Skyline Advisor, vmware, vSphereLeave a comment

VMware has had a product for a while now called VMware Skyline that provides proactive monitoring, analysis, and support for your VMware environment. It monitors your VMware installation and will notify you when issues arise.

Skyline Advisor will be available to customers and partners with active Production and Premier Support, VMware Success 360 and vRealize Cloud Universal subscriptions at no additional cost.

Create a Cloud Services Organization

https://console.cloud.vmware.com/

After clicking Get Started, a new web browser page, or tab, will open. You will be asked to sign-in

with your VMware account. If you have an existing My VMware account, you can use those same

account details (email address/password) to sign in to Cloud Services.

If you are existing VMware Cloud Services customer, you can choose an existing Cloud Services

Organization for Skyline. If you have never used VMware Cloud Services, click Create New

Organization.

Enter a Organization Name.

Name your Organization something meaningful, that can be easily

referenced by both you, and VMware. For example, name your Organization after you Company, or

Business name. You can also append a line-of-business, division, or team, to the end of your

Company or Business name.

The following are example Organization Names:

The company, LOB, Company LOB, Company-vSphere, Company-Desktop

Enter an Address for your Organization.

Click Add Address. You can also choose an existing

address if one was found for your account. If you choose an existing address, skip to substep f.

During the creation of your Cloud Services Organization, your country currency, and Tax ID, may be

displayed. The displaying of this information is a construct of Cloud Services. Skyline is available at

no additional cost, and you will not be required to enter any payment details while adopting Skyline.

Select a Country from the drop-down menu.
Enter your street address on Address Line 1, and Address Line 2 (optional).
Enter your City.
Enter your State/Province.
Enter your Zip/Postal Code.
Review the Cloud Services Terms of Service. Click the checkbox to agree to the Terms of Service.
Click Continue.

Now on service, we have Skyline Advisor, click on this service

Link the Entitlement

Now, after clicking on LINK, we have the correct status LINKED

**Deploy Skyline Collector and configure the connection to Cloud Services**

Now we download the Skyline collector
https://vmware.com/go/skyline-collector-download

To deploying the Skyline Collector Virtual appliance on our vSphere infrastructure we have need:

And these are the Network Requirements

Account permission for vCenter, we need to create a Domain Account to use to permit access to vCenter from skyline.

Let’go we are starting with the OVF Deploy

After deployed the Connector virtual appliance we need to configure the Skyline Collector for communicating with Cloud Services

Test the network configuration

And now we have to insert the token create on Cloud Service

Get Token from Vmware Cloud Services Platform

Download VMware Skyline Collector
Select Version:
•roduct Downloads
Product
VMware Skyline is an innovative proactive support offering that brings high-performing technology and tools to the workbench to
radically transform customer support
Automatically and securely collect product usage data with VMware Skyline Collector. Environment-specific analytics based on
configuration, feature, and performance data are executed against this data. The resulting information may radically improve
Read More
Product Resources
View My Download History
Product Info
Documentation
Community
Drivers & Tools
Open Source
Custom ISOS
VMware Skyline Collector 28.0
OEM Addons
Release Date
2021-07-15
GO TO DOWNLOADS — **Deploy Skyline Collector and configure the connection to Cloud Services**

Now we download the Skyline collector
https://vmware.com/go/skyline-collector-download

To deploying the Skyline Collector Virtual appliance on our vSphere infrastructure we have need:

And these are the Network Requirements

Account permission for vCenter, we need to create a Domain Account to use to permit access to vCenter from skyline.

Let’go we are starting with the OVF Deploy

After deployed the Connector virtual appliance we need to configure the Skyline Collector for communicating with Cloud Services

Test the network configuration

And now we have to insert the token create on Cloud Service

Get Token from Vmware Cloud Services Platform

VMware Cloud Services

I have already configured my organization

Copy and paste the token on Skyline Connect and register it.

Add source Data to Skyline Advisor

After complete the step 5 and 6 (I suggest to enable the auto-upgrade), we can access to skyline collector to configure the connection to vCenter (or multiple vCenter)

Go to https://<mySkylineCollectorFQDN/

Select Add a vCenter Server

Use the Account AD to whom assign the correct permission on vCenter

We are able to see the vSphere infrastructures if we access on Skyline Advisor Service on Cloud Service Link

https://console.cloud.vmware.com/

Now we will be waiting….. for data populate (72 hours for Findings)

After 72 hours we are able to see all info (wow I see six Critical alerts :-))

VMware Skyline Frequently Asked Questions (55928)

Skyline Collector User Accounts and Permissions (vmware.com)

Allineamento Azure SQL DB

October 28, 2019 fabioAzure, Azure SQL DB, Azure SQL Server, BACPAC, cloud, import, Microsoft, SqlPackage.exeLeave a comment

Lavorando con i servizi Azure SQL Server/Azure SQL DB e ambienti di DEV/QTY/PRD può capitare la necessità di allineare i dati e le struttura dei DB.

Ho provato due scenari di ripristino da un file BACPAC:

Portale Azure
SqlPackage.exe

Per la mia esperienza consiglio l’utilizzo di SqlPackage.exe il motivo principale è che in questa maniera non dovrete:

Dipendere da quanti utenti stanno eseguendo procedure di importazione DB nella vostra region.
Se utilizzare, come spero, i servizi Firewall inclusi sugli azure sql server non avrete necessità di abilitare l’accesso da indirizzi IP “sconosciuti”
Non avrete limiti di dimensione del DB che volete importare.

Come funziona l’importazione da Portale Azure? Qui la guida ufficiale

Prima di procedere è necessario prendere in considerazione questi aspetti:

Viene messa a disposizione una “Machine” (tutto automatico e trasparente per il sistemista) con al massimo 405GB. Ma per completare l’importazione sarà necessario 3 volte la dimensione del BACPAC che dovete importare. Quindi se la matematica non è un opinione la dimensione massima del file dovrà essere 150GB
Può capitarvi un errore simile:

è necessario abilitare sul firewall del Azure SQL Server di destinazione l’IP evidenziato

Può succedere che per caricare un DB di dimensioni ridotte siano necessarie delle ore. Tenete conto che il processo di creazione dipende da quante richieste di importazione nella region sono state effettuate (non solo da voi ma da tutto il mondo), perchè la richiesta viene accodata e poi quando è il vostro turno (ma non è dato di sapere) verrà processata. Come indicato in questo link ufficiale. Se dopo 4 giorni non è stata processata la tua richiesta di import viene cancellata

Per avviare l’importazione è necessario:

– Caricare il file bacpac su un container su Azure Storage Account

– Accedere via portale all’azure SQL Server e selezionare la voce:

– Configurare i vari parametri

– Lanciare l’importazione

Per monitorarla è possibile farlo Import/Export History

Se vi collegate con SSMS al Azure SQL Server vedrete che il DB viene creato immediatamente, appena parte il job di importazione, ma poi il job rimane in pending e le tabelle e i dati non vengono popolati… il tutto rimane in attesa del proprio turno di importazione

Come funziona l’importazione da SqlPackage.exe? Qui la guida ufficiale

Avete la necessità di:

Scaricare il SqlPackage e installarlo
Abilitare una VM per l’accesso all’azure Sql Server (sempre il discorso del Firewall), ma in teoria una VM di Management dovreste già averla..

– Da powershell dovete utilizzare il seguente comando:

.SqlPackage.exe /a:Import /sf:<percorso-del-bcapac> /tsn:<Azure SQL Server> /tdn:<Nome del DB> /tu:<Account> /tp:<Password> /p:DatabaseEdition=<Standard/basic ecc> /p:DatabaseServiceObjective=<es. S2>

Il comando se il DB non esiste lo crea …

Al termine di entrambi i processi ricordatevi di:

– Eliminare le credenziali sql non necessarie

– Dare i permessi alle credenziali sql necessarie

-Sistemare i backup

Antispam in cloud cosa aspettarsi

April 18, 2014 fabioantispam, archive, Backup, cloud, mail, mail continuity, posta, security, spamLeave a comment

Negli ultimi anni si sente sempre di più parlare di cloud e di servizi in cloud. In questo post non voglio entrare nel dettaglio di cos’è il cloud e se esistono veramente dei servizi che si posso definire in cloud, voglio solamente focalizzarmi su un di quei servizi, che con l’avvento del cloud e quindi del suo utilizzo in cloud aumenta la sua efficacia e aumentano le sue potenzialità.
Stiamo parlando dell’antispam.

L’utilizzo di un antispam nella nuvola ci permette di parlare non solo di blocco delle mail indesiderate ma anche di

Riduzione del traffico in ingresso
Mail continuity
Backup mail o archive mail

Riduzione del traffico in ingresso
Spostando il servizio di antispam dalla propria infrastruttura al cloud il traffico delle mail viene filtrato prima che raggiunga il nostro server di posta, e quindi la banda occupata in ingresso diminuisce annullando quasi del tutto quel traffico indesiderato generato dalla mail di spam. Quindi solo le mail puilite arrivano in ingresso al nostro server interno

Mail continuity (A volte già incluso in altri casi da pagare in aggiunta al servizio di antispam)
Quante volte ci è capitato di avere il server di posta offline (Aggiornamento, crash del sistema operativo etc.. ) e dover rispondere al nostro amministratore delegato che la mail che sta aspettando non può arrivare e non sappiamo quando arriverà. Con la mail continuity nel caso di offline del nostro mail server interno, la posta rimane sul nostro antispam in cloud, e quindi può essere consultata dall’amministratore di sistema e con alcuni mail security cloud provider ogni nostro singolo utente può accedere a una web mail e vedere la propria posta (Si può passare da un minimo di 3/4 giorni di “capacità” del servizio in cloud anche a due e piu’ settimane)

Mail Backup o Archive (Servizio che in alcuni casi può essere compreso oppure puo’ essere in aggiunto coma add-on a pagamento)

Il passo di avere in un datacenter di altro livello, quindi in un posto “al sicuro”, un contenitore che ci controlla lo spam e ci pemrmette una sorta di HA della mail ci porta anche a valutare la possibilità di poter archiviare/salvare la mail temporaneamente o all’infinito nel cloud. Altro plus, in alcune versioni, la possibilità di delegare al nostro utente finale la visione e il recupero delle mail.

Non ho citato, ma ovviamente è da considerare come vantaggio la diminuzione dell’attivita’ dell’amministratore IT nella gestione del servizio.

CLOUD = no server da mantenere (che sia fisico o virtuale), no servizio antispam da mantenre (aggiornamento o upgrade di versione)

Mantenendo ovviamente le caratteristiche di base in un classico antispam:

Controllo delle mail in ingresso e in uscita

Controllo antivirus (in molti casi anche con piu’ di un motore)

Gestione personalizzate di blacklist e del livello di filtro dello spam

Gestione della quarantena a livello dell’amministratore ma anche dell’utente finale.

Quindi il cloud è sicuramente per il servizio di antispam un valore aggiunto.