Windows 10: Microsoft announces generally available release of PowerShell 7.0

Brink · Mar 4, 2020

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?

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 https://aka.ms/pslifecycle

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/

Tweet

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

:)

Brink · Mar 4, 2020

#AzureAD PowerShell V2.0 is now Generally Available

Howdy folks,

About a month ago, we announced an updated public preview for PowerShell Azure AD v2.0.

Today I’m happy to announce that these PowerShell Azure AD v2.0 cmdlets are now generally available (GA)!

To give you a rundown on the improvements we’ve made since we released the preview, I’ve asked Rob de Jong to blog about them. You’ll find his blog below.

I hope you will find these cmdlets useful. And as always, we would love to receive any feedback or suggestions you have!

Best Regards,

Alex Simons (Twitter: @Alex_A_Simons)
Director of Program Management
Microsoft Identity Division

—-

Hi everyone,

It’s Rob de Jong here and today I’m excited to let you know that Azure AD PowerShell v2.0 is now GA and to give you a quick tour of the changes we’ve made since the previous public preview. This release marks an important milestone in the Azure AD PowerShell because now you can leverage the new cmdlets in this module in your production environments.

One request customers have consistently made is that we make sure we maintain equivalent capabilities between our Graph API and our PowerShell cmdlets. To make sure that happens, all these new cmdlets are built on top of the Graph API.

Two important notes:

The new Azure AD PowerShell v2.0 module don’t provide full functional parity with the older MSOL module yet. We’re working hard to make that happen in the coming months and will keep you updated on our progress.

We are not planning to publish new functionality in the MSOL PowerShell module. Over time we will implement all the functionality of the old MSOL cmdlets in the new module, and this new module contains quite a few new cmdlets that haven’t been available before.

Changes since the preview

We’ve made a few changes to some of the cmdlets since the previous preview release of Azure AD PowerShell v2.0:

Naming conventions: The Revoke-AzureADSignedInUserAllRefreshTokens and Revoke-AzureADUserAllRefreshTokens were renamed to Revoke-AzureADSignedInUserAllRefreshToken Revoke-AzureADUserAllRefreshToken respectively to follow the Verb-SingularNoun naming convention.

Excluded cmdlets: This GA only includes cmdlets that call into a production endpoint of the Graph API. If you want to use cmdlets that call a Beta endpoint, these are available in the public preview release of the Azure AD v2.0 PowerShell cmdlets. The cmdlets excluded from this release include those used to manage Administrative Units, Domain settings, Policy settings, and Directory settings.

To find a list of all cmdlets included in this release, please refer to the Azure AD v2.0 general availability release notes.
How to deploy

To install the new module, follow this link to the PowerShell Gallery. Installing a PowerShell module from the PowerShell gallery requires some additional components to be installed on your system. If you are running a computer with the Windows 10 OS, these components are already present and you can simply open a PowerShell window as an administrator and type “Install-Module AzureAD”, The module will be installed on your computer and imported in your session.

For other Windows operating systems, please refer to the documentation about the PowerShell Gallery.

Getting help with this module

If you need more information about how these cmdlets work, the easiest way to get it is to use the inline help functionality. Here is an example of how to do that, using the Get-Help cmdlet:

For online help, you can also refer to the Azure AD v2.0 PowerShell module online documentation.

We’re here to help

If you need any help with a specific solution you’re trying to create, have feedback you want to share, or have questions for which the answer cannot be found in the documentation, please send an email to L: AADPS@Microsoft.com. We’ll get back to you as soon as we can and look forward to hearing from you!

Regards,

Rob
Click to expand...

Source: #AzureAD PowerShell V2.0 is now GA Enterprise Mobility and Security Blog

btarunr · Mar 4, 2020

Microsoft Announces Windows 7 Retail Prices Ahead of General Availability

Microsoft unveiled the retail pricing structure of its upcoming Windows 7 operating system, and its three important variants: Home Premium, Professional, and Ultimate, elaborating on the pricing on both the upgrade and full versions. Microsoft also announced that customers buying PCs pre-installed with existing versions of Windows from select sources (retailers or OEMs), will be able to upgrade to Windows 7 at "little or no cost". The company also announced that select retailers in certain markets will be able to offer for a limited period of time, a pre-order discount scheme that can reduce the price by as much as 50 percent.

Here are the prices (in USD):

Windows 7 Home Premium - $199.99 (full version), $119.99 (upgrade)

Windows 7 Professional - $299.99 (full version), $199.99 (upgrade)

Windows 7 Ultimate - $319.99 (full version), $219.99 (upgrade)

Microsoft also detailed the global availability of the OS, and in different languages. The English version will launch on October 22. PC OEM vendors will be able to start shipping PCs pre-installed with the OS on the same day. Apart from the English version, Windows 7 in Spanish, Japanese, German, French, Italian, Dutch, Russian, Polish, Brazilian Portuguese, Korean, Simplified Chinese, Traditional Chinese and Chinese (Hong Kong), will be available on the same day. Windows 7 in Turkish, Czech, Portuguese, Hungarian, Swedish, Danish, Norwegian, Finnish, Greek, Ukrainian, Romanian, Arabic, Lithuanian, Bulgarian, Estonian, Slovenian, Hebrew, Thai, Croatian, Serbian Latin, and Latvian, will be available on October 31.

Source: The Windows Blog

Brink · Mar 4, 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

Windows 10: Microsoft announces generally available release of PowerShell 7.0

Microsoft announces generally available release of PowerShell 7.0

Microsoft announces generally available release of PowerShell 7.0

Microsoft announces generally available release of PowerShell 7.0

Microsoft announces generally available release of PowerShell 7.0 - Similar Threads - Microsoft announces generally

General Availability of PowerShell 7.2

Announcing Microsoft Edge WebView2 General Availability

Microsoft announces general availability of Desktop Analytics

Microsoft Teams PowerShell Module General Availability

The Next Release of PowerShell - PowerShell 7

Announcing General Availability of Microsoft 365 Business apps

Announcing Azure DNS General Availability

Announcing general availability of Upgrade Readiness

Announcing Microsoft BizTalk Server 2016 general availability