Norio Sashizaki
My feedback
-
7 votes
An error occurred while saving the comment -
314 votestriaged · 11 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
-
186 votes
We continue to investigate this. Due to the current roadmap and strategy this will remain in our backlog. Please continue to share feedback related to this topic to help us make an informed decision at a later time.
-
8 votesunder review · 1 comment · Azure Monitor-Log Analytics » Mobile App · Flag idea as inappropriate… · Admin →
-
25 votes0 comments · Azure Monitor-Log Analytics » Solutions / Packs Gallery and new IP ideas · Flag idea as inappropriate… · Admin →
This isn’t really a prioritized scenario at this point, as we don’t really bring all of the OpsMgr data to the cloud, but only for specific scenarios (to which you can opt in/out by adding/removing ‘intelligence packs’).
I updated the category of this idea to match it is a new Intelligence Pack/scenario suggestion.
-
3 votes3 comments · Azure Monitor-Log Analytics » Solutions / Packs Gallery and new IP ideas · Flag idea as inappropriate… · Admin →
‘owned’ currently means ‘added’ to this workspace.
We got the term for consistency with how it says in the Windows Store, but there is no concept of a ‘user’ acquiring an IP and then adding it to the workspace(s). You always just add it to the workspace and that’s it.But we’ll consider a better/clearer terminology if this is unclear, thanks for the feedback.
You seem to like just ‘Added’?
-
13 votesunder review · 3 comments · Azure Monitor-Log Analytics » Browser Support · Flag idea as inappropriate… · Admin →
-
34 votes0 comments · Azure Monitor-Log Analytics » Workspace Settings / Administration · Flag idea as inappropriate… · Admin →
Currently, you can add your users fro the ‘settings’ page and invite either LiveID or AAD users/groups to access the workspace directly from https://preview.opinsights.azure.com/
You can have direct agents and SCOM management groups that live in different subscriptions than the one the workspace is linked to. The only scenario that is limited at the moment is ingesting data from storage accounts (WAD data). We are investigating for how many this is important enough to allow cross-subscription reading of Storage accounts.
Also read this other thread for an additional requirement we have heard in this area http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519233-improve-multitenancy-for-managed-services-provider#comments
-
41 votes7 comments · Azure Monitor-Log Analytics » Agent Management (OnPrem components) / Connectivity / Setup · Flag idea as inappropriate… · Admin →
In the current implementation, Management groups CAN already be removed, but only once they are ‘stale’ == have not reported ANY data for >14days, the link to remove will appear.
The number of Directly reporting agents in ‘settings’ page is the actual number of servers registered, but the drill down will take you to search (where servers presence is inferred from the data).
We will be working on options to de-register directly connected servers, similarly to we offer for SCOM management groups.
An error occurred while saving the comment Thank you, I understand.
See my blog.
http://sshzk.blogspot.com/2015/05/azure-backup-on-windows-server-2012.html