Survey message

[dcaro]

We are planning to invite users of Azure PowerShell to provide feedback from within the tool once or twice a year at most.
The message will be displayed after the command output only once, we want to make it visible but not intrusive.

We worked with our design team and have narrowed it down to few options for which we would like to get your vote.

Option 1 - Text in white with blue background with a padding line before and after

Option 2 - Text in black with gray background with a padding line before and after

Option 3 - Text in white with blue background with no padding line, command and hyperlink in yellow

Option 4 - Text in black with gray background with no padding line, command and hyperlink in blue

[brwilkinson]

My preference is to use an alternate strategy for getting feedback. These types of scheduled tasks/events can cause issues in the console.

It's quite frustrating just to get these messages when you are trying to work, however when there are related issue e.g. with psreadline or oh-my-posh Etc. it becomes even more problematic.

• If this is implemented, ideally please ensure there is an opt out, that includes not having any background jobs or schedule events etc.

My preferences would be:

• Opt into a newsletter which was something generic for having a communication channel with users.

  • Such as "AZ PowerShell Community Newsletter".
    • Then send out surveys as part of the newsletter as an opt in. Or links to surveys from there,
    • That way you can click it when you are not in the middle of working and it's more user friendly overall.

• Otherwise having survey links from Twitter is also user friendly.

[EwertonJordao]

Or channels on discord/slack/teams to include surveys.

[arjanbroeke]

Or like the update message, when you start your pwsh session.

[dcaro]

Really appreciate the feedback! We considered several options and selected the one displaying the message after a command has been executed because adding a dependency on the shell or relying on forums / socials medias would have introduced a bias in the base that we would get feedback from.
One can argue that there is a small bias with our approach since we will only collect feedback from users who have upgraded but we think this is small enough.

Regarding the capability to disable it, the mechanism will be controlled by an AzConfig parameter and an environment variable. We are also working on disabling it by default in environments that we know like Azure DevOps, Azure Automation or GitHub actions so that you do not have to worry about having additional settings.

[brwilkinson]

More options

• Option 5 - Text in white with blue background with a padding line before and after, command and hyperlink in yellow

I like the colored yellow links on the blue background, plus the extra lines ... so not sure if that is an option?

[kilasuit]

This seems to be implying that as part of a profile the azure modules will be loaded, which is often not the case

Some admins will have them loaded as part of their profile, most however, won't.

This should only be shown on completion of the Connect-AzAccount cmdlet, in my opinion, for the best & least intrusive user experience.

[dcaro]

Thanks everyone for your comments and votes, option 1 has been selected.
To address some concerns expressed above, the message can be disabled to not pollute automation environments. The team reads every feedback that will be provided through this mechanism and will help prioritize and define the future of the Azure PowerShell modules.

The balance between collecting actionable feedbacks and not disrupting your workflow is important to us so please open issues on any behavior related to this change that gets in your way.