Menu
We have added Application Insights to our app, but I'm unable to make the application insights data availible to other developers (azure users). This is what I've tried:
Application insights data is showing up fine in my portal, problem is that my colluages are not able to locate the resource or the resource group in her azure portal. I've tried by sending a link, but the azure portal just says "loading"
Question is: Do I need to give some other access to allow for sharing application insights?
Thanks for any help
Larsi
846
Browse to the Azure portal. Select All services to open Application Insights. Then, search for Application Insights. Under Subscriptions, select a subscription that has Application Insights resources and then under Name, select one or more applications.
After publishing the dashboard, select Manage sharing. In Access Control select Role assignments to see existing users that are already assigned a role for this dashboard. To add a new user or group, select Add then Add role assignment. Select the role that represents the permissions to grant, such as Contributor.
Since you mention "developer" I'm assuming you are both using separate MSDN subscriptions, and thats whats causing the issue. If this is the scenario that you are each using your own MSDN subscriptions when you log in, the other developer need to "switch" to your "directory" after they sign in, in order to see the things you gave them access to. Once the other dev is logged in to the azure portal, have them click their name in the upper right of the browser window, and in that dropdown there will likely be an additional "directory" that they can select which effectively switches them to see things that are inside your subscription+directory. Its this extra level of the "Directory" that is probably hiding your AI resource from him. I experienced this problem first hand in the exact scenario you have described.
163
There is a lot of information about setting up access control for Application Insights here: https://azure.microsoft.com/en-us/documentation/articles/app-insights-resources-roles-access-control/
It looks like you've done most of those things, but you might want to double check just in case. Also, you shouldn't need to assign them "contributor", which would allow them to edit things, you should only need to give them "reader" access so they can see the data.
41
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
