Update overview

* Related to #5
* Users were not clear on which Service Connection type was able to be used

Author: JoshuaTheMiller

docs/Overview.md

@@ -2,6 +2,12 @@
 
 Use a [service connection][serviceConnection] with scripts instead of pasting secrets into variables!
 
+### ❗ *Important note on using Service Connections* ❗
+
+Please note that these tasks are built to only use `Generic` Service Connections. No other connections will be displayed when configuring these tasks. This is due to how Service Connections function in Azure DevOps- `Generic` is a "well-known" connection type as it is built into the platform, and thus can be reliably referenced by these tasks 🙂 
+
+Please see the following GitHub Issue if more detail is needed: [LINK](https://github.com/cloudpups/authenticated-scripts/issues/5)
+
 ## Features
 
 * ✅ Supply Generic Service Connection to a PowerShell script
@@ -67,4 +73,4 @@ Instances of folks asking for this:
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-[serviceConnection]: https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml
+[serviceConnection]: https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml