How do you go about addressing individual resistance to cloud?

When addressing individual resistance to the cloud, it is important to understand the reasons behind the resistance. Common reasons include fear of the unknown, lack of knowledge and understanding, security concerns, and cost.

Once the root cause of the resistance has been identified, it is important to provide education and resources to help allay the fears and doubts. This can include providing information on cloud security, cost savings, and potential applications of cloud technology. Additionally, offering demonstration or trial services can help show individuals the potential of the cloud. Finally, it is important to provide a safe, comfortable environment to discuss any concerns or issues.

The main issue is training and costs. When teams get educated about these further, the resistance will reduce.

In general "what is in it for me" or "What is in it for the organisation" needs to be as clear as it can be to reduce the resistance. Unless people are not sold or if they have a tangentially different opinion about the transformation ( case in point here is Cloud), they will resist.
Ability to articulate the big picture, opportunity to up skill, ability to perform and scale seamlessly, ability to reduce the burn or do more for less or same,.... there are more data points that can be shown to make the people see through the lens that an Org sees.

Resistance comes from a place of responsibility and care, so the first step of the process should be that all major stakeholders that will be using the new cloud infrastructure will be actively involved in how this should be set up.

Both from a user and maintenance perspective. When people get a chance to ask their questions and raise their concerns the resistance becomes much lower.

The path of least resistance in moving to cloud is to start with a greenfield workload. Teams are reluctant to move their existing workloads in many instances for good reasons. And with good reasons in many cases. Leaders are often looking for cost savings in their largest and most complicated applications, seeing that they are often also the most resource intensive - and therefore also presenting the greatest cost saving opportunities. But to start there is often a 'bridge too far'. Instead, if an organisation starts a new project cloud-first with a team / individuals who will be tasked with migration an existing workload to the cloud, then they can build up confidence and best-practise experience building their first cloud application. The next step for them would be to migrate an existing workload to the cloud. This step-by-step approach would give the team(s) to confidence to move more workload to the cloud.