@JonDouglas @chgill-MSFT

The message we have been using for all scenarios is:

You are running the 'xyz' operation with an 'HTTP' source, 'http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json'. Support for 'HTTP' sources will be removed in a future version.

As discussed in the meeting, we don't really have say move to https. I'd appreciate any guidance on what you'd propose adding here.
We'd need to review messages for a single and for more than one source.

Here's my first stab:

Single source:

You are running the 'xyz' operation with an 'HTTP' source, 'http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json'. Support for 'HTTP' sources will be removed in a future version. Take the necessary steps to migrate to HTTPS instead.

Multiple sources:

You are running the 'xyz' operation with 'HTTP' sources, 'http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json; http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json'. Support for 'HTTP' sources will be removed in a future version. Take the necessary steps to migrate to HTTPS instead.

cc @martinrrm @kartheekp-ms

I like the single source and that you added the "action" to change to HTTP, but for the multiple sources, is it possible to do a multiline warning?

You are running the 'xyz' operation with 'HTTP' sources:
'http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json'
'http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json'

Support for 'HTTP' sources will be removed in a future version. Take the necessary steps to migrate to HTTPS instead.

Something like that, I'm worried about readability when there are a lot of sources but given that users don't use a lot of HTTP sources I'm fine with your proposal.

I think the newline is a good idea.

@nkolev92

Single source:

You are running the 'xyz' operation with an 'HTTP' source, 'http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json'. Non-HTTPS access will be removed in a future version. Consider migrating to an 'HTTPS' source.

Multiple sources:

You are running the 'xyz' operation with 'HTTP' sources: 

http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json

http://localhost:49350/c56f0fe1-7835-4a72-b5d3-761069e2515f/index.json

Non-HTTPS access will be removed in a future version. Consider migrating to 'HTTPS' sources.

That looks good to me.

Do you think we should use newlines for the multi source one?

For sure. If we can organize these things more than on a single line, it would be more effective & glanceable. Fixed my original message as I didn't realize the intention till now.

Pushed a change with the updated messages.