Forum Discussion
Sharing Environment Resources with Multiple projects within Organization in ADO
Hi,
Do we have any updates or improvements over sharing Environment Resources with multiple projects within the organization in ADO. Have gone through some discussions but none of them suggest or show a way for the above scenario. When we type in for the same question in google the AI responds saying " can share environment resources across different projects by utilizing features like "variable groups" and "deployment groups". How correct it is and kindly share with me if anyone has done this. Thanks
3 Replies
Have a question on another topic regarding azuredevops limitation to use RSA tokens with 256 or 512 for ssh connections. These keys are deprecated and prone to security risks. The limitation I am talking about is in the below document
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Frepos%2Fgit%2Fuse-ssh-keys-to-authenticate%3Fview%3Dazure-devops&data=05%7C02%7CMamatha_Daggubati%40bcbst.com%7C99b30eb1f2af4e0cf04008dd80ce23b0%7C68503c37a9634410afcaecaad3d96f17%7C1%7C0%7C638808345032410176%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=rMFHKQ8s9optZezxNmcisxnBusl2orz81j8cNc8K3y4%3D&reserved=0Thank you for your information Maxwell.
It is recommended to segregate environments according to their purpose such as development, staging production and so on to prevent issues in one environment from infecting others. Particularly you should isolate your production instance from lower environments. Having a separate subscription in which development work occurs can be cost saving in that you can easily manage the lifecycle of development artifacts.
