The use-case:

• A large enterprises scale on organizations (in Azure DevOps these units of scale are more correctly called 'Projects').
• Inner-source communities for shared libraries and reusable components typically follow the guidelines GitHub share for open-source code, but remove the benefit of anonymous access to public repos. There is no such construct in GHEC. Repos are internal or private. Clue is multi organization setup.
• A team has code that takes dependency on resources from one or more inner-source community that has created language based libraries to make teams more efficient internally.

Question:
How can we use OCTO-STS to grant workflow access to other organizations?