Cross-Company Collaboration
COSMO Alpaca allows that both you and your customers, partners, freelancers, etc. can work together on the same project.
WIP
Please note that the tenant an Azure DevOps organization is connected to, determines the billed party.
Inviting external users to collaborate with Alpaca
- For COSMO organizations only: Access to COSMO Alpaca needs to be granted for the tenant of the external user first. Please contact the Alpaca support to do so.
- For COSMO organizations only: Files on the fileshare that are referenced as dependencies need to be copied over from your own to the customer specific fileshare. You'll get access information about the customer specific fileshare in step 1.
- You need to allow guest access and invite the external users into the organization.
Please note that external users now need to switch to your tenant to work in your organization and might want to create separate VS Code profiles if they use Alpaca in multiple tenants.
Use Alpaca in an Azure DevOps organization in a customer tenant
If your customer wants to have the Azure DevOps organization to reside in their own tenant, you can follow the following steps.
- Create a new Azure DevOps organization or migrate an existing organization to the customer tenant by following the steps outlined in the documentation.
- Access to COSMO Alpaca needs to be granted for the customer tenant first. Please gather the customer's tenant ID and contact the Alpaca support to do the setup.
- You need to allow guest access and invite all your users into the organization and give Basic Access Level to developers. Please note that the customer is billed for all User licenses.
- The customer's IT needs to approve the Alpaca app in their tenant. Change the following URL to include the customer's tenant ID and ask a customer admin to use it to approve the Alpaca app:
https://login.microsoftonline.com/<tenant-id>/adminconsent?client_id=abed730b-114e-47a8-b905-1e116382469e - If you want to do the project and repository setup for your customer you need to be organization admin. Now do all the necessary project and app setup like normally.
- Files on the fileshare that are referenced as dependencies need to be present on the customer specific fileshare. You'll get access information about the customer specific fileshare in step 2.
Please note that developers now need to switch to the customer tenant to work in the customer organization and should create different VS Code profiles for the different tenants.