Windows 10: Microsoft releases Secret Management Preview 2 module for PowerShell

Brink · Mar 20, 2020

We are excited to release a second preview of the Secret Management Module. Thanks to the tremendous feedback we received from the first preview release of this module, you will notice a number of breaking changes to the module. This release is still a preview release meaning that it is not feature complete, future releases will face breaking changes, and we are still iterating based on your feedback. It is important to also note that this version of the module is still Windows only as we are currently implementing Linux support which we hope to make available in the next preview release (and MacOS support after). Please note that because of the breaking changes this release requires a complete replacement of the Secret Management module and any extension modules. Additionally, any existing built in local vault secret can no longer be retrieved and must be re-saved.

How to Install Secret Management Preview 2

If you did not install our first preview release, open any PowerShell console and run:

Install-Module Microsoft.PowerShell.SecretManagement -AllowPrerelease

If you installed our first preview release you will want to first remove any secrets from the LocalDefaultVault. Based on feedback we changed the naming convention for secrets stored in CredMan, therefore previous secrets stored in the local vault will no longer be visible after the new version of the module is installed. (Although the user can still view/remove the old secrets via CredMan UI.) Next you will want to run Uninstall-Module Microsoft.PowerShell.SecretsManagement, this extra step is a result of the change we made to the name of the module. Finally you can run the above command Install-Module Microsoft.PowerShell.SecretManagement -AllowPrerelease to install the latest preview release of the module.

Changes in Secret Management Preview 2

New Module Name

We have removed the plurality in the module name to Mirosoft.PowerShell.SecretManagement in order to be consistent with the cmdlet name and to align with PowerShell naming conventions.

New Cmdlet Names

In addition to renaming the module, we have also removed plurality in the cmdlets. The available cmdlets in the module are now:

Code:

# Registering extension vaults
Register-SecretVault
Get-SecretVault
Unregister-SecretVault
Test-Vault # new cmdlet in this release

# Accessing secrets
Set-Secret # this cmdlet replaces Add-Secret
Get-Secret
Get-SecretInfo
Remove-Secret
Click to expand...

You will notice we renamed the Add-Secret cmdlet to be Set-Secret. This change was based on user feedback that this name better conveyed the intention of the cmldet.

You will also notice that we have added a Test-Vault cmdlet, this change allows vault extension owners to check that the vault is properly configured at registration time.

Other Changes

Set-Secret now has a default parameter set that takes SecureString secret input type. This way Set-Secret will always prompt safely for a SecureString. String secret types can still be passed via parameter or pipeline, but default will be SecureString.

Code:

PS> Set-Secret -Name MyStringToken
cmdlet Set-Secret at command pipeline position 1 Supply values for the following parameters:
SecureStringSecret: **********

# Set string secret directly
Set-Secret -Name MyStringToken -Secret $token
Set-Secret -Name MyStringToken -Secret 'MyToken'
# Set string secret via pipeline
$token | Set-Secret -Name MyStringToken -NoClobber
Click to expand...

Added SecretInformation class used to return information from Get-SecretInfo in a uniform way.

Changed CredMan naming prefix to ps:SecretName.

Added vaultName to all vault extension functions.

Fixed additionalParameters parameter in SecretManagementExtension abstract classes.

Fixed return byte[] bug in example test script extension.

In coordination with these changes we have also updated our tests and example scripts.

Next Steps

As we move towards a GA release later this year, we are using a GitHub Milestone to track issues we plan to fix. The two major work items that we are currently working toward are:

Linux Support (via keyring)

MacOS Support (via keychain)

Support and Feedback

For support on the module, feedback, or reporting a bug, please open an issue in the PowerShell/modules repo with â(Secrets Management)â specified in the issue title.
Sydney Smith, PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...iew-2-release/

:)

Brink · Mar 20, 2020

Microsoft Teams PowerShell Module General Availability

We are excited to announce the general availability of the Microsoft Teams PowerShell module. This PowerShell module, first released in Beta last year, allows you to manage the lifecycle of teams within your organization. As a Global Administrator or Teams Service Administrator, you can identify and manage teams on behalf of your users, and make bulk updates to teams faster – including changing memberships or managing team settings. This new version of our module leverages only 1.0 Graph APIs.

Going forward, we will be maintaining both a Preview and Generally Available versions of the Microsoft Teams PowerShell module. This will allow us to deliver new, preview functionality to our customers faster for testing, while ensuring that our Generally Available module continues to leverage only 1.0 APIs.

The following cmdlets are supported in our generally available module:

[table][tr][td]Cmdlet[/td] [td]Description[/td] [/tr] [tr][td]Connect-MicrosoftTeams[/td] [td]Connects an authenticated account to use for Microsoft Teams environment[/td] [/tr] [tr][td]Disconnect-MicrosoftTeams[/td] [td]Disconnects from the Microsoft Teams environment[/td] [/tr] [tr][td]Get-Team[/td] [td]Retrieves teams with particular properties or information[/td] [/tr] [tr][td]Get-TeamChannel[/td] [td]Gets all the channels for a team[/td] [/tr] [tr][td]Get-TeamHelp[/td] [td]Provides a list of commands for Microsoft Teams[/td] [/tr] [tr][td]Get-TeamUser[/td] [td]Returns the users of a specific team[/td] [/tr] [tr][td]New-Team[/td] [td]Provisions a new Team, or converts a group to a team[/td] [/tr] [tr][td]New-TeamChannel[/td] [td]Adds a new channel to a team[/td] [/tr] [tr][td]Add-TeamUser[/td] [td]Adds an owner or member to the team[/td] [/tr] [tr][td]Remove-Team[/td] [td]Deletes a team[/td] [/tr] [tr][td]Remove-TeamChannel[/td] [td]Delete a channel[/td] [/tr] [tr][td]Remove-TeamUser[/td] [td]Removes an owner or member from a team[/td] [/tr] [tr][td]Set-Team[/td] [td]Updates properties of a team[/td] [/tr] [tr][td]Set-TeamChannel[/td] [td]Update Team channel information[/td] [/tr] [/table]

Additional Functionality in New Release

In addition to leveraging solely 1.0 APIs, we have made a few improvements to cmdlets in the Generally Available module:

Connect-MicrosoftTeams: You can now specify a Teams Government Environment (-TeamsEnvironmentName) that your organization is homed in.

Get-Team: We expanded the filter and selection criteria to include properties such as the Visibility or Archived state of the teams so that you can more easily identify teams that may require your attention

Simplified Experience

To improve the discoverability of certain team settings, we consolidated the functionality of the following cmdlets into the Get-Team and Set-Team cmdlets:

- Get-TeamFunSettings
- Get-TeamGuestSettings
- Get-TeamMemberSettings
- Get-TeamMessagingSettings
- Set-TeamFunSettings
- Set-TeamGuestSettings
- Set-TeamMemberSettings
- Set-TeamMessagingSettings

Note: These beta cmdlets will not be available in future module releases

Want to learn more about PowerShell?

Because Teams is built on top of different services, PowerShell controls for Teams are split across several modules. Learn more about PowerShell for Teams (also includes links to the technical docs for individual cmdlets).

Let us know what you think!

If you have suggestions on how to make Teams better, please submit your idea via User Voice or vote for existing ideas to help us prioritize the requests. We read every piece of feedback that we receive to make sure that Microsoft Teams meets your needs.

— Christopher Bryan, Microsoft Teams
Click to expand...

Source: Microsoft Teams PowerShell Module General Availability - Microsoft Tech Community - 480934

Brink · Mar 20, 2020

Microsoft Teams PowerShell Module General Availability

We are excited to announce the general availability of the Microsoft Teams PowerShell module. This PowerShell module, first released in Beta last year, allows you to manage the lifecycle of teams within your organization. As a Global Administrator or Teams Service Administrator, you can identify and manage teams on behalf of your users, and make bulk updates to teams faster – including changing memberships or managing team settings. This new version of our module leverages only 1.0 Graph APIs.

Going forward, we will be maintaining both a Preview and Generally Available versions of the Microsoft Teams PowerShell module. This will allow us to deliver new, preview functionality to our customers faster for testing, while ensuring that our Generally Available module continues to leverage only 1.0 APIs.

The following cmdlets are supported in our generally available module:

[table][tr][td]Cmdlet[/td] [td]Description[/td] [/tr] [tr][td]Connect-MicrosoftTeams[/td] [td]Connects an authenticated account to use for Microsoft Teams environment[/td] [/tr] [tr][td]Disconnect-MicrosoftTeams[/td] [td]Disconnects from the Microsoft Teams environment[/td] [/tr] [tr][td]Get-Team[/td] [td]Retrieves teams with particular properties or information[/td] [/tr] [tr][td]Get-TeamChannel[/td] [td]Gets all the channels for a team[/td] [/tr] [tr][td]Get-TeamHelp[/td] [td]Provides a list of commands for Microsoft Teams[/td] [/tr] [tr][td]Get-TeamUser[/td] [td]Returns the users of a specific team[/td] [/tr] [tr][td]New-Team[/td] [td]Provisions a new Team, or converts a group to a team[/td] [/tr] [tr][td]New-TeamChannel[/td] [td]Adds a new channel to a team[/td] [/tr] [tr][td]Add-TeamUser[/td] [td]Adds an owner or member to the team[/td] [/tr] [tr][td]Remove-Team[/td] [td]Deletes a team[/td] [/tr] [tr][td]Remove-TeamChannel[/td] [td]Delete a channel[/td] [/tr] [tr][td]Remove-TeamUser[/td] [td]Removes an owner or member from a team[/td] [/tr] [tr][td]Set-Team[/td] [td]Updates properties of a team[/td] [/tr] [tr][td]Set-TeamChannel[/td] [td]Update Team channel information[/td] [/tr] [/table]

Additional Functionality in New Release

In addition to leveraging solely 1.0 APIs, we have made a few improvements to cmdlets in the Generally Available module:

Connect-MicrosoftTeams: You can now specify a Teams Government Environment (-TeamsEnvironmentName) that your organization is homed in.

Get-Team: We expanded the filter and selection criteria to include properties such as the Visibility or Archived state of the teams so that you can more easily identify teams that may require your attention

Simplified Experience

To improve the discoverability of certain team settings, we consolidated the functionality of the following cmdlets into the Get-Team and Set-Team cmdlets:

- Get-TeamFunSettings
- Get-TeamGuestSettings
- Get-TeamMemberSettings
- Get-TeamMessagingSettings
- Set-TeamFunSettings
- Set-TeamGuestSettings
- Set-TeamMemberSettings
- Set-TeamMessagingSettings

Note: These beta cmdlets will not be available in future module releases

Want to learn more about PowerShell?

Because Teams is built on top of different services, PowerShell controls for Teams are split across several modules. Learn more about PowerShell for Teams (also includes links to the technical docs for individual cmdlets).

Let us know what you think!

If you have suggestions on how to make Teams better, please submit your idea via User Voice or vote for existing ideas to help us prioritize the requests. We read every piece of feedback that we receive to make sure that Microsoft Teams meets your needs.

— Christopher Bryan, Microsoft Teams
Click to expand...

Source: Microsoft Teams PowerShell Module General Availability - Microsoft Tech Community - 480934

Brink · Mar 20, 2020

Microsoft announces generally available release of PowerShell 7.0

Today, we’re happy to announce the Generally Available (GA) release of PowerShell 7.0! Before anything else, we’d like to thank our many, many open-source contributors for making this release possible by submitting code, tests, documentation, and issue feedback. PowerShell 7 would not have been possible without your help.

What is PowerShell 7?

For those unfamiliar, PowerShell 7 is the latest major update to PowerShell, a cross-platform (Windows, Linux, and macOS) automation tool and configuration framework optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models. PowerShell includes a command-line shell, object-oriented scripting language, and a set of tools for executing scripts/cmdlets and managing modules.

Three years ago, we announced PowerShell Core 6 as a completely new edition of PowerShell. Built on top of .NET Core, PowerShell Core introduced cross-platform support across Windows, macOS, and Linux, SSH-based PowerShell Remoting, massively improved support for REST and JSON, official Docker containers, and more. Additionally, it was the first release of PowerShell made under an open-source license (MIT), encouraging long-time PowerShell enthusiasts and complete newcomers alike to contribute directly to the source code, tests, and documentation.

After three successful releases of PowerShell Core, we couldn’t be more excited about PowerShell 7, the next chapter of PowerShell’s ongoing development. With PowerShell 7, in addition to the usual slew of new cmdlets/APIs and bug fixes, we’re introducing a number of new features, including:

Pipeline parallelization with ForEach-Object -Parallel

New operators:

Ternary operator: a ? b : c

Pipeline chain operators: || and &&

Null conditional operators: ?? and ??=

A simplified and dynamic error view and Get-Error cmdlet for easier investigation of errors

A compatibility layer that enables users to import modules in an implicit Windows PowerShell session

Automatic new version notifications

The ability to invoke to invoke DSC resources directly from PowerShell 7 (experimental)

For a more complete list of features and fixes, check out the PowerShell 7.0 release notes.

The shift from PowerShell Core 6.x to 7.0 also marks our move from .NET Core 2.x to 3.1. .NET Core 3.1 brings back a host of .NET Framework APIs (especially on Windows), enabling significantly more backwards compatibility with existing Windows PowerShell modules. This includes many modules on Windows that require GUI functionality like Out-GridView and Show-Command, as well as many role management modules that ship as part of Windows. For more info, check out our module compatibility table showing off how you can the latest, up-to-date modules that work with PowerShell 7.

If you weren’t able to use PowerShell Core 6.x in the past because of module compatibility issues, this might be the first time you get to take advantage of some of the awesome features we already delivered since we started the Core project!

Awesome! How do I get PowerShell 7?

How to Install PowerShell 7.0 in Windows 7, Windows 8, and Windows 10

First, check out our install docs for Windows, macOS, or Linux. Depending on the version of your OS and preferred package format, there may be multiple installation methods.

If you already know what you’re doing, and you’re just looking for a binary package (whether it’s an MSI, ZIP, RPM, or something else), hop on over to our latest release tag on GitHub.

Additionally, you may want to use one of our many Docker container images. For more information on using those, check out our PowerShell-Docker repo.

What operating systems does PowerShell 7 support?

PowerShell 7 supports the following operating systems on x64, including:

Windows 7, 8.1, and 10

Windows Server 2008 R2, 2012, 2012 R2, 2016, and 2019

macOS 10.13+

Red Hat Enterprise Linux (RHEL) / CentOS 7+

Fedora 29+

Debian 9+

Ubuntu 16.04+

openSUSE 15+

Alpine Linux 3.8+

Additionally, we support ARM32 and ARM64 flavors of Debian and Ubuntu, as well as ARM64 Alpine Linux.

While not officially supported, the community has also provided packages for Arch and Kali Linux.

If you need support for a platform that wasn’t listed here, please file a distribution request on GitHub (though it should be noted that we’re ultimately limited by what’s supported by .NET Core 3.1).

Wait, what happened to PowerShell “Core”?

Much like .NET decided to do with .NET 5, we feel that PowerShell 7 marks the completion of our journey to maximize backwards compatibility with Windows PowerShell. To that end, we consider PowerShell 7 and beyond to be the one, true PowerShell going forward.

PowerShell 7 will still be noted with the edition “Core” in order to differentiate 6.x/7.x from Windows PowerShell, but in general, you will see it denoted as “PowerShell 7” going forward.

Which Microsoft products already support PowerShell 7?

Any module that is already supported by PowerShell Core 6.x is also supported in PowerShell 7, including:

Azure PowerShell (Az.*)

Active Directory

Many of the modules in Windows 10 and Windows Server (check with Get-Module -ListAvailable)

On Windows, we’ve also added a -UseWindowsPowerShell switch to Import-Module to ease the transition to PowerShell 7 for those using still incompatible modules. This switch creates a proxy module in PowerShell 7 that uses a local Windows PowerShell process to implicitly run any cmdlets contained in that module. For more information on this functionality, check out the Import-Module documentation.

For those modules still incompatible, we’re working with a number of teams to add native PowerShell 7 support, including Microsoft Graph, Office 365, and more.

Azure Cloud Shell has already been updated to use PowerShell 7, and others like the .NET Core SDK Docker container images and Azure Functions will be updated soon.

How is PowerShell 7 officially supported by Microsoft?

As with PowerShell Core, PowerShell 7 is a supported product for a wide range of customers with existing Microsoft support agreements.

With PowerShell 7, we’re moving to a support lifecycle whereby we match the lifecycle of the underlying .NET runtime that we distribute as part of PowerShell. This means that PowerShell 7.0 is a long-term servicing (LTS) release that will be supported for approximately 3 years from December 3, 2019 (the release date of .NET Core 3.1).

You can find more info about PowerShell’s support lifecycle at PowerShell Core Support Lifecycle - PowerShell

What’s next for PowerShell?

We’re already hard at work on PowerShell 7.1, and you should expect its first preview soon, chock full of new features and bugfixes that didn’t quite make it into 7.0. Stay tuned for a more in-depth roadmap blog outlining our current investigations and desires for 7.1.

As noted above, we’re also moving to an annual release cadence in order to align better with .NET releases and their support lifecycle (with previews continuing to release roughly every month).

How can I give feedback on PowerShell 7?

For most issues directly related to PowerShell 7, start by filing an issue on the main PowerShell repository. For issues related to specific modules (e.g. PSReadline or PowerShellGet), make sure to file in the appropriate repository.

Thanks again!

Much appreciation to everyone involved in this release, from multi-time contributors all the way to those of you keeping up with our preview releases. We couldn’t have done it without you!
Joey Aiello

PM, PowerShell
Click to expand...

Source: https://devblogs.microsoft.com/power...owerShell-7-0/

How to Install PowerShell 7.0 in Windows 7, Windows 8, and Windows 10

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: Microsoft releases Secret Management Preview 2 module for PowerShell

Microsoft releases Secret Management Preview 2 module for PowerShell

Microsoft releases Secret Management Preview 2 module for PowerShell

Microsoft releases Secret Management Preview 2 module for PowerShell

Microsoft releases Secret Management Preview 2 module for PowerShell - Similar Threads - Microsoft releases Secret

PowerShell 7.2.0 preview 2 released

PowerShell 7.2.0 preview 1 released

PowerShell 7.1.0 preview 7 released

PowerShell 7.1.0 preview 6 released

PowerShell 7.1.0 preview 5 is released

Powershell 7.1 preview 5 is released

Powershell 7.1 preview 4 is released

PowerShell 7.1.0 preview 3 released

Powershell 7.1 preview 2 is released