Technical Tip: Both FortiManager/FortiAnalyzer Cloud instances must be deployed in the same region

[heng]

Description	This article describes how to fix the warning that appears when a user is trying to deploy the next subsequent FortiManager/FortiAnalyzer Cloud instance to a different region. Both FortiManager/FortiAnalyzer Cloud instances MUST be deployed in the same region for the same account ID.  As of now, below are the currently available regions for FortiManager/FortiAnalyzer Cloud instance deployment: Asia Pacific (Tokyo). Canada (Vancouver). Germany (Frankfurt). United States (San Jose). Example of use case: Set up or deploy the FortiManager/FortiAnalyzer Cloud instance for the first time under the account. There is a FortiManager instance in one region, deployed, e.g., the United States (San Jose), successfully. Next, if the FortiAnalyzer instance is deployed in another region, say Asia Pacific (Tokyo), the following warning will appear in the deployment: Your account has already deployed FortiManager in the region of United States (San Jose). Please switch to United States (San Jose) region for the deployment.
Scope	FortiManager/FortiAnalyzer Cloud Customer portal: FortiManager Cloud  FortiAnalyzer Cloud
Solution	Under the provision service region, correct the region to the same region as the first instance deployed, e.g., here to the United States (San Jose): In case the region with a FortiManager or a FortiAnalyzer Cloud already deployed for the FortiCloud email user is not listed among the regions available to deliver new instances, it means that it is temporarily not possible deliver new Instances on it. In that case, follow this article: Technical Tip: How to request for FortiManager/FortiAnalyzer Cloud instance migration to a different... to migrate the existing instance to a more convenient instance, among those available to create new ones