Update docs.microsoft.com links (#12653 )

# PR Summary

* remove explicit en-us from links
* remove view parameter


## PR Context

follow-up #7013

## PR Checklist

- [x] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
    - Use the present tense and imperative mood when describing your changes
- [x] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [x] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [x] This PR is ready to merge and is not [Work in Progress](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---work-in-progress).
    - If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the title (the `WIP` bot will keep its status check at `Pending` while the prefix is present) and remove the prefix when the PR is ready.
- **[Breaking changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)**
    - [ ] None
    - **OR**
    - [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/6/Microsoft.PowerShell.Core/About/about_Experimental_Features.md)
        - [ ] Experimental feature name(s): <!-- Experimental feature name(s) here -->
- **User-facing changes**
    - [x] Not Applicable
    - **OR**
    - [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
        - [ ] Issue filed: <!-- Number/link of that issue here -->
- **Testing - New and feature**
    - [x] N/A or can only be tested interactively
    - **OR**
    - [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting)
- **Tooling**
    - [x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
    - **OR**
    - [ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
        - Impact on [PowerShell Editor Services](https://github.com/PowerShell/PowerShellEditorServices) which is used in the [PowerShell extension](https://github.com/PowerShell/vscode-powershell) for VSCode (which runs in a different PS Host).
        - Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
        - Impact on [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) (which provides linting & formatting in the editor extensions).
        - Impact on [EditorSyntax](https://github.com/PowerShell/EditorSyntax) (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

2020-05-15 03:29:43 +00:00

4.3 KiB

Raw Blame History

Adopters

This is a list of adopters of using PowerShell in production or in their products (in alphabetical order):

Azure Cloud Shell provides a batteries-included browser-based PowerShell environment used by Azure administrators to manage their environment. It includes up-to-date PowerShell modules for Azure, AzureAD, Exchange, Teams, and many more. More information about Azure Cloud Shell is available at Azure Cloud Shell Overview.
Azure Functions - PowerShell is a serverless compute service to execute PowerShell scripts in the cloud without worrying about managing resources. In addition, Azure Functions provides client tools such as Az.Functions, a cross-platform PowerShell module to manage function apps and service plans in the cloud. For more information about Functions, please visit functions overview.
PowerShell Universal Dashboard is a cross-platform web framework for PowerShell. It provides the ability to create robust, interactive websites, REST APIs, and Electron-based desktop apps with PowerShell script. More information about PowerShell Universal Dashboard is available at the PowerShell Universal Dashboard Docs.
System Frontier provides dynamically generated web GUIs and REST APIs for PowerShell and other scripting languages.
Enable non-admins like help desk and tier 1 support teams to execute secure web based tools on any platform without admin rights.
Configure flexible RBAC permissions from an intuitive interface, without a complex learning curve.
Script output along with all actions are audited. Manage up to 5,000 nodes for free with the Community Edition.
Amazon AWS supports PowerShell in a wide variety of its products including AWS tools for PowerShell, AWS Lambda Support For PowerShell and AWS PowerShell Tools for CodeBuild as well as supporting PowerShell Core in both Windows and Linux EC2 Images.
Azure Resource Manager Deployment Scripts Complete the "last mile" of your Azure Resource Manager (ARM) template deployments with a Deployment Script, which enables you to run an arbitrary PowerShell script in the context of a deployment. Designed to let you complete tasks that should be part of a deployment, but are not possible in an ARM template today — for example, creating a Key Vault certificate or querying an external API for a new CIDR block.
Azure Pipelines Hosted Agents Windows, Ubuntu, and MacOS Agents used by Azure Pipelines customers have PowerShell pre-installed so that customers can make use of it for all their CI/CD needs.
GitHub Actions Virtual-Environments for Hosted Runners Windows, Ubuntu, and MacOS virtual environments used by customers of GitHub Actions include Powershell out of the box.
Windows 10 IoT Core is a small form factor Windows edition for IoT devices and now you can easily include the PowerShell package in your imaging process.

4.3 KiB Raw Blame History

Adopters

4.3 KiB

Raw Blame History