AzureFileCopy@5 : 9 Different Warnings

[DaleyKD]

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

Enter Task Name: AzureFileCopy@5

Environment

• Server - Azure Pipelines
• Agent - Hosted

Issue Description

• Both Az and AzureRM modules were detected on this machine. Az and AzureRM modules cannot be imported in the same session or used in the same script or runbook. If you are running PowerShell in an environment you control you can use the 'Uninstall-AzureRm' cmdlet to remove all AzureRm modules from your machine. If you are running in Azure Automation, take care that none of your runbooks import both Az and AzureRM modules
• The names of some imported commands from the module 'Microsoft.Azure.PowerShell.Cmdlets.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter.
• The names of some imported commands from the module 'Az.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter.
• The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead.
  

[mstjernfelt]

+1

[robkendrick]

Note that you can make the 'Get-SpnAccessToken' warning disappear by adding the following to your pipeline YAML:

variables:
  USE_MSAL: true 

Ref: #17677

[sabifa]

+1 just ran into these warnings

[ciuliene]

Any update on other warnings?

[reedijkbart]

+1 I get the first warning all the time.

[lopezbertoni]

+1 I get the first warning all the time.

[julienLemarie]

Hello,

Still many warnings on this task:

2024-02-01T16:32:18.0100924Z ##[warning]Both Az and AzureRM modules were detected on this machine. Az and AzureRM modules cannot be imported in the same session or used in the same script or runbook. If you are running PowerShell in an environment you control you can use the 'Uninstall-AzureRm' cmdlet to remove all AzureRm modules from your machine. If you are running in Azure Automation, take care that none of your runbooks import both Az and AzureRM modules. More information can be found here: https://aka.ms/azps-migration-guide

2024-02-01T16:32:27.7740245Z ##[warning]Upcoming breaking changes in the cmdlet 'Clear-AzConfig' :
Parameter `DisableErrorRecordsPersistence` will be deprecated, a new parameter `EnableErrorRecordsPersistence` will be added instead. Writing error records to file system will become opt-in instead of opt-out. This change will happen around May 2024
- The change is expected to take effect in Az version : '12.0.0'
- The change is expected to take effect in Az.Accounts version : '2.X'
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.

2024-02-01T16:32:44.2925678Z ##[warning]The names of some imported commands from the module 'Microsoft.Azure.PowerShell.Cmdlets.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.

2024-02-01T16:32:44.5917580Z ##[warning]The names of some imported commands from the module 'Az.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.

2024-02-01T16:32:45.2027043Z ##[warning]You're using Az.Resources version 6.5.1. The latest version of Az.Resources is 6.14.0. Upgrade your Az modules using the following commands:
  Update-Module Az.* -WhatIf    -- Simulate updating your Az modules.
  Update-Module Az.*            -- Update your Az modules.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[palhal]

I still think this should be looked at, although i decided to use the AzureCLI task instead in combination with the az storage blob upload command. I don't want these kind of warnings in production.