As a Service Operator, you are responsible for adherence to the terms of the InCommon Participation Agreement, including the InCommon community's Baseline Expectations, as they evolve to address the changing IAM ecosystem over time.
Understand your clients within the research and education community. Partnering with a new cloud service client can be complicated and time-consuming. Nearly all of the hurdles can be overcome with technical or policy solutions, but forming those solutions can be an expensive process that diminishes the value proposition of adopting your service in the first place. Understanding collaboration and federation in research and education and Sharing the Burden of User Support are useful resources.
Understand the multilateral federation community. Multilateral federation is an evolving field. See Engage - get the most out of InCommon for how to stay current.
If you have outsourced software development and/or platform operation, you remain responsible to the community for the issues described in Building InCommon-Ready Software and Make Your Platform Federation Ready. Make sure that your partnerships enable you to do that, particularly if the partnership involves a legal agreement.