219 votes34 comments · Azure Active Directory » Groups/Dynamic groups · Flag idea as inappropriate… · Admin →
Our feature team is looking into options for addressing this scenario, but we do not yet have any timelines to share. For now as a workaround, you can manually trigger the reprocessing by updating the membership rule to add a whitespace at the end. We’ve also added the ability to check the membership processing status, to keep track of the status and know if processing is complete.
41 votes1 comment · Azure Monitor-Log Analytics » Solutions / Packs Gallery and new IP ideas · Flag idea as inappropriate… · Admin →
Thanks for the idea.
46 votes0 comments · Azure Monitor-Log Analytics » Solutions / Packs Gallery and new IP ideas · Flag idea as inappropriate… · Admin →
We’re continuing to investigate options for adding this support. There are technical challenges to overcome in order to make this happen. We thank you for all your valuable comments so far, and welcome any additional feedback you have on what are the most important use cases involved with these scenarios.
We are starting investigation to make this integration happen. We will update you as we progress on the feature and when we have a release date. Thank you so much for your patience.
Send a note to firstname.lastname@example.org if you have questions!
Just adding another message of support for this change. I have two customers running RDS2016 via Azure AD App Proxy, clients for both are forced into using IE11 due to the ActiveX component which is not ideal. Moving these clients to the HTML5 version via the Azure AD Proxy would increase adoption of the platforms significantly. Eagerly awaiting this!
88 votes6 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
Any update on this? It seems like Custom Field extraction has been in preview forever! It's a very powerful component of Log Analytics which needs just a little more polish before being able to use it on a larger scale.
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
I've largely ignored this problem/limitation as working with a few dozen deployments now exclusively windows, it seems the Windows 2012 R2 OS works rather well with the Azure portal recovery/troubleshooting tools and the requirement for console access has never left me stranded.
Linux however, is another story. I'm now working on a predominantly Linux deployment and we've had a couple of issues now with VM's that we cannot access, due to booting into emergency/maintenance mode and expecting a prompt from the user at console level.
We get a screenshot telling us exactly what the problem is, but this is just brings an added level of frustration. So close, yet so far.
A further update to this feedback suggestion would be most welcome.
Thanks for submitting this request. We are currently investigating how to make this possible. We will update you once it has made to our backlog.
We are working with Azure on enabling this.
Kindly give us more requirements or your experiences with current failback from Azure so that we address them holistically.
To allow redundancy external to Azure, for workloads that do not support HA/availability sets etc.
Thank you for the feedbacks. Ensure that the experience requirements are mentioned in the comments.
Being forced to support a workload in Azure that doesn't support any kind of HA/load balancing due to the software, it would be very useful to have an ASR scenario which would allow me to replicate live Azure workloads to an on-premise host.
Thanks, Stephen. Let’s see a few more votes on this and see the popularity.