Thank you so much for your response.

We dont prefer to keep the notebooks under Shared or run our jobs pointing to the Shared location. We have more than 200 applications and different teams working on them. Each application has a service principal associated with it and only the service principal has access to the specific applications volume and schema.

Based on your response, we are planning to follow the below approach.

1. Create notebooks under personal user account

2. Push the code to GIT

3. Deploy using bundles

4. In the bundles, provide the run_as AS service principal so that the jobs are owned and run using the service principal. 

Questions:

1. Do you think this is a good approach for notebook based implementation or do you suggest anything else?

2. The service principal exists only in Databricks, so what email and PAT should be provided to enable GIT access? 3. How will service principal get access to the Azure GIT repo (ADO repository)? 

4. Is there any other access that the service principal needs for this approach, for bundles etc ?