Bring your own subscription (BYOS) enables you to participate in a Microsoft OpenHack using your own Azure subscription(s). The documentation in this repository provides guidance on how to setup each OpenHack in your subscription as well as an overview of some of the differences you will see when interacting with the coach and attendee portals of OpenHack when using your own subscription.
Contents
Setup of environment may take extensive time depending on the OpenHack topic you are running. For safe measure, please start running the OpenHack on your Azure subscription(s) at least 48 hours before the kickoff of the event.
OpenHack participants work together as a team (usually around 5-6 people per team). In the diagrams below you will see user accounts specified as [email protected]. You can optionally use generated accounts in that format just for the OpenHack or you can use your users real user accounts.
There are two common approaches for setting up subscriptions and permissions for an OpenHack.
Option 1: Azure subscription per team
This approach provides ownership access at the subscription level for OpenHack participants. This approach is the most open and flexible method to allow attendees to use the widest range of tools at their disposal to complete the OpenHack. The tradeoff is attendees have full control over any resource that can be created in the subscription.
Option 2: Azure Resource Group per Team
This approach provides ownership access at the resource group level for each team participating in the OpenHack. This approach allows finer control of what attendees can/cannot do during the OpenHack. You can optionally apply policies to control which services are available at the subscription scope which are not overridable at the resource group level.
Most OpenHacks do not require additional permissions in Azure AD. The Migration OpenHack is the current exception and requires Global Administrator permissions. It is not recommended to run this OpenHack in a production Azure AD tenant.
The following documents outline the permissions needed for each OpenHack, the most common resources that are created, as well deployment script documentation if the OpenHack has resources that should be created prior to the start.
- AI-Powered Knowledge Mining
- App Modernization with NoSQL
- Containers
- DevOps
- DevOps for Data Science Retired as of June 30, 2021
- Dynamics 365 + Power Platform Retired as of June 30, 2021
- Iot Gateway Operations Retired as of June 30, 2021
- Migration
- Modern Data Warehousing
- Serverless
- Security, Compliance, and Identity
In a BYOS OpenHack, the Azure subscriptions are managed completely out of the Opsgility environment. The following, outlines the differences you will experience in the Cloud Sandbox/Coach Portal and the attendee portal in a BYOS OpenHack environment.
The differences you will encounter on the Cloud Sandbox is as a Tech Lead or a Lead PM/Coach:
- You will no longer have the ability to start or end the lab environment. This is because the Azure subscriptions in a BYOS scenario are not controlled by the Cloud Sandbox.
- You will not have the ability to view view the Azure credentials for the environments. Access to the Azure subscriptions must be managed in the Azure AD tenant you will use for the BYOS environment.
The difference you will encounter on the Attendee portal is you will not see the View Lab Environment tab with your Azure user credentials. Access to the Azure subscription in managed on the Azure AD tenant you will use for the BYOS environent.
- OpenHack Program: Contact us @ [email protected]
- Opsgility Portals Contact us @ [email protected]