Enable Cisco SD-AVC Cloud Connector, Cisco Catalyst SD-WAN Manager Release 20.14.1 and Later

Updated: July 7, 2026

Want to summarize with AI?

Information about enabling Cisco SD-AVC Cloud Connector, Cisco Catalyst SD-WAN Manager Release 20.14.1 and later.

Before Cisco Catalyst SD-WAN Manager Release 20.14.1, client ID, client secret credentials, and sometimes a cloud gateway URL and OTP were required to enable Cloud Connector. From Cisco Catalyst SD-WAN Manager Release 20.14.1, you can configure Cisco SD-AVC Cloud Connector using the Cloud Services page. With this feature, you need not retrieve an OTP or create a TAC case separately to enable SD-AVC Cloud Connector.

Before you begin

Enable Cisco SD-AVC under Administration > Cluster Management to enable Cloud Connector.

Procedure

	1.	From the Cisco SD-WAN Manager menu, choose Administration > Settings.
	2.	Select Cloud Services.
	3.	Enable Cloud Services in the Cloud Services tab. From Cisco Catalyst SD-WAN Manager Release 20.18.2, after you enable Cloud Services, click Register in the Cisco services onboarding popup that appears and enter your Smart Account credentials. Alternatively, from Cisco Catalyst SD-WAN Manager Release 20.18.2, you can authenticate for Cloud Services from the Cisco services registration page.
	4.	Enter your Smart Account credentials.
	5.	(Optional) Enable Analytics. Note Enable this option only if you have deployed Cisco Catalyst SD-WAN Analytics, and have confirmed that it is reachable by Cisco SD-WAN Manager.
	6.	Enable SD-AVC Cloud Connector. Note If Cisco SD-WAN Manager is cloud-hosted by Cisco, this option does not appear and Cloud Connector is enabled automatically after you enable the Cloud Services option.
	7.	Click Save.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.