338 votesunder review · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
The status of this item has been moved back to Under Review. We initially planned to move to VHDX support as part of our support for HyperV Gen2 VMs, but we ended up using the VHD format for Gen2 VMs as well. Some aspects of the Azure Infrastructure do not cleanly support VHDX OS or data disks. So this feature is dependent on some of these internal services being updated which is an ongoing process.
Thanks for posting this suggestion!
Connection types are defined as a file in the module file. Is there a reason that you want to created them via cmdlets instead?
As a side note, you can do this through our API today as a workaround.
It would be nice to have a way to create a connection type from Powershell without the need to upload a module, if users have not seen the blog post on how to create a connection type, when they look through the powershell cmdlets they will find a way to create the connection type.
Thanks for this suggestion. Yes, as you mentioned & Joe explained this is a known issue in SMA and Azure Automation, but there are workarounds now.
We can use this request to track making connection types mutable.
Thanks for posting this idea. The team is looking into this. I’ll update when we start working on this feature.
Thanks for posting this feedback.
We’re adding more validation to the blade to avoid this. Thanks for the feedback.
I think the correct solution to this is to create a mount point on the C drive for the page file. this allows the users to have full control of the disk drives and any changes made at the fabric layer don't impact the users.
Please add a setting so we can control what drive is used. When testing with a v2 VM if you change the temp storage drive to the first available drive letter it appears that it does not cause any issues when the VM is resized, still doing some more testing.
10 votes1 comment · Azure Monitor-Log Analytics » Workspace Settings / Administration · Flag idea as inappropriate… · Admin →
I passed along the feedback to the team.
Since there are different Azure service teams triaging these, could you also cross-post in the automation forum?
Great feedback. We are looking at potentially delivering a solution in this area. Thank you!
27 votes0 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
Windows Server 2003 and before were using TEXT log files http://support.microsoft.com/kb/168801
Windows Server 2008 and beyond use ETL traces – http://blogs.msdn.com/b/clustering/archive/2008/09/24/8962934.aspx
Also refer to these generic ideas:
Text log files collection tracked here http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/7113030-collect-text-log-files
Collection of ETW traces is tracked here http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6691402-collect-etw-trace-logs
278 votes3 comments · Azure Monitor-Log Analytics » Solutions / Packs Gallery and new IP ideas · Flag idea as inappropriate… · Admin →
Can you provide a RANKED list of what is MOST and LEAST important for the various capabilities and scenarios that SM provides? i.e. you listed
- problem management
- incident management
- configuration items