FortiSOAR MT_RegionalSOC license type in v7.6.0 in comparison with v7.5.0

[malayamanas]

Hello FortiSOAR Team,

I do not find reference to FortiSOAR MT_RegionalSOC license type in v7.6.0 in comparison with v7.5.0.

Please refer to below two links and compare.

In v7.6.0 there is no reference to FortiSOAR MT_RegionalSOC license type.

Is this FortiSOAR MT_RegionalSOC license discontinued in v7.6.0 ? If not then provide corresponding documentation reference.

What will be the impact for existing FortiSOAR MT_RegionalSOC license deployed?

V7.5.0 Web Reference: https://docs.fortinet.com/document/fortisoar/7.5.0/deployment-guide/223944/licensing-fortisoar#/docu...

V7.6.0 Web Reference: https://docs.fortinet.com/document/fortisoar/7.6.0/deployment-guide/223944/licensing-fortisoar#/docu...

Thanks

Malaya Manas

[anarula]

@malayamanas is your observation solely based on documentation? or did you face some problem?

anyway, all previously multi tenant licenses are supported with v7.6.0 as well.

The naming has been simplified/made-more-intuitive. See this part in 7.6.0 documentation:

• If the 'Role' is set as "Tenant (Multiple user capable)", then the instance is enabled as a "Tenant (Multiple user capable)" deployment at an organization that has a distributed SOC, and which is a complete SOAR platform. At the same time, it can be configured as a "tenant" to the global SOC where the "Multi-Tenant (Manager)" license is deployed and sync data and actions from the Global SOC FortiSOAR server. For more information of what multi-tenancy is and what master nodes are, see the "Multi-tenancy support in FortiSOAR Guide."

[malayamanas]

@anarula Thank you for your response.

My observation is based on documentation as we do not have luxury of spending unnecessary time finding issues later into the project, then creating TAC ticket, talking to TAC person, and  following up, it burns our energy without achievement.

I find V7.6.0 has significant changes for licensing and there is no reference to previous keywords like MTT(Master), MTD(Destributed Tenant, which can not have another MTD under it), MTR (Regional SOC Destributed Tenant, which can have another MTD under it)

Please work to make the documentation backwardly compatible with the understanding and any omissions should be replaced with a new reference to any other document.

Thank You 

Malaya Manas 

[nmathur]

@malayamanas I have created a doc mantis to add the mapping of the licensing name updates to the 7.6.0 docs. Once updated I will republish the document

[nmathur · Accepted solution]

@malayamanas : We have enhanced the License Manager documentation (did not introduce any new terminologies for the licenses) to align with the existing terminology in the Ordering Guide since the introduction of the multitenant SKUs. This change simplifies the process for customers referencing the ordering guide when purchasing license SKUs.
Additionally, I have updated and republished the guide to include the previous license type names.
https://docs.fortinet.com/document/fortisoar/7.6.0/deployment-guide/223944/licensing-fortisoar#Licen...

@anarula : FYI