- Added warning logs to detect Az context switching in Get-AzFunctionApp
- Enabled support to create Node 18 Preview and Java 17 Preview function apps (fixes issues #19184 and #18925)
- Removed the logic that checks for AzureGermanCloud in the cloud endpoints (fixes issue #19667)
- Hided generated unused cmdlets (fixes #16666)
- Fixed an issue that New-AzFunctionApp cmdlet should write a warning message when setting default values for parameters that are not provided.
- Exposed PowerShell 7.2 stack definition for function app creation in Functions V4 only
- Removed preview from the PowerShell 7.0 stack on Linux
- [Breaking change]
Update-AzFunctionAppPlan
prompts for confirmation [#16490] - [Breaking change]
Remove-AzFunctionApp
does not delete ASP if it is the last app in the plan [#16487] - [Breaking change] Set the
FunctionsVersion
to 4 for FunctionApp creation [#16426] - [Breaking change]
Update-AzFunctionApp
prompts for confirmation [#14442] - Fixed an error creating function with
New-AzFunctionApp
on PowerShell 5.1 [#15430] - Supported storage account SKU
Standard_GZRS
[#14633]
- Set site config netFrameworkVersion for Windows V4 apps only
- Enabled function app creation for Functions V4 stacks [#15919]
- Added two additional app settings (WEBSITE_CONTENTSHARE and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING) for Linux Consumption apps. [15124]
- Fixed bug with New-AzFunctionApp when created on Azure Gov. [13379]
- Added Az.Functions cmdlets need to support creating and copying app settings with empty values. [14511]
- Added support in function app creation for Python 3.9 and Node 14 function apps
- Removed support in function app creation for V2, Python 3.6, Node 8, and Node 10 function apps
- Updated IdentityID parameter from string to string array in Update-AzFunctionApp. This is to be consistent with New-AzFunctionApp which has the same parameter as a string array
- Updated FullyQualifiedErrorId for an invalid Functions version from FunctionsVersionIsInvalid to FunctionsVersionNotSupported
- When creating a Node.js function app, if no runtime version is specified, the default runtime version is set to 14 instead of 12
- [Breaking Change] Removed
IncludeSlot
switch parameter from all but one parameter set ofGet-AzFunctionApp
. The cmdlet now supports retrieving deployment slots in the results when-IncludeSlot
is specified. - Updated
New-AzFunctionApp
:- Fixed -DisableApplicationInsights so that no application insights project is created when this option is specified. [#12728]
- [Breaking Change] Removed support to create PowerShell 6.2 function apps.
- [Breaking Change] Changed the default runtime version in Functions version 3 on Windows for PowerShell function apps from 6.2 to 7.0 when the RuntimeVersion parameter is not specified.
- [Breaking Change] Changed the default runtime version in Functions version 3 on Windows and Linux for Node function apps from 10 to 12 when the RuntimeVersion parameter is not specified.
- [Breaking Change] Changed the default runtime version in Functions version 3 on Linux for Python function apps from 3.7 to 3.8 when the RuntimeVersion parameter is not specified.
- Removed the ability to create v2 Functions in regions that do not support it.
- Deprecated PowerShell 6.2. Added a warning for when a user creates a PowerShell 6.2 function app that advises them to create a PowerShell 7.0 function app instead.
- Added support to create PowerShell 7.0 and Java 11 function apps
- General availability of 'Az.Functions' module
- the first preview release