33 votes3 comments · Azure Monitor-Log Analytics » Agent Management, Data Metering and Usage (Portal) · Flag idea as inappropriate… · Admin →
We have a public preview of solution targeting available:
Try it out and let us know what you think.
This would be huge for us as well and would help us to onboard many more nodes. Please consider adding this feature as soon as possible!
We’re looking at using information from the Windows Security Center to collect status from non-Microsoft antimalware products.
Thanks for posting this suggestion! Our team has looked at this in the past and having your vote for this feature helps us prioritize adding it.
Thanks for this feedback. We will take a look.
Also, do you have an example of a command that you are trying to use right now? I’ve heard of other customers managing Exchange & O365 with Automation, so there might be a different way to perform the task you are trying to do.
Beth: I have tried both workarounds with limited success. After running the script in Azure using Import-Session I tried using Invoke-Command and had no luck. Next I tried running the script on a hybrid worker (using Import-Session) and had success.
Then I scheduled it to continue running on a hybrid worker and after 5 days it stopped working and began returning the same exception as before - "The job action 'Activate' cannot be run, because the process stopped unexpectedly. The job action was attempted 3 times."
It just seems really inconsistent at this point and I can't find any rhyme or reason. I believe there is some issue with the execution engine and implicit remoting but can't really say what.
Sorry, I realize that this is not a support forum but I thought I should elucidate the issue a bit.
Interesting - I hadn't thought about just using Invoke-Command. I'll try that and see if it works.
Does this serve as a confirmation that implicit remoting is not possible in Azure Automation?
I'm just using the commands detailed here
to connect to Exchange Online, and there's a similar command to connect to the Compliance Center, which also uses an Exchange implicit remoting session.
It seems to just spin on the Import-PSSession command and the verbose log message states:
"Importing function 'Update-roleGroupMember'..."
this repeats over and over as each remote command is received. Eventually something happens and the job is suspended with this exception:
"The job action 'Activate' cannot be run, because the process stopped unexpectedly. The job action was attempted 3 times"
I found this blog:
Where it states that Automation can't deal with importing commands from a remote session, but so far I haven't found this detailed anywhere in the Automation documents.
Thanks for posting this suggestion! You are right that this is a larger work item, but something that could really help with debugging. Having your & the community vote for it helps our team prioritize the work though, so even if its a tall order its great for us to get the feedback.
Thanks for this feedback. Until complete Intelllisense is available, you may want to take a look at the PowerShell ISE add-on for Automation: https://github.com/azureautomation/azure-automation-ise-addon and https://www.powershellgallery.com/packages/AzureAutomationAuthoringToolkit/.