Error `Unable to encode the output with cp1252 encoding.` is shown when logging in to a subscription which name contains Japanese characters and on Windows runner

[horihiro]

When trying to log in with a subscription which name contains Japanese characters by the following simple workflow, the logging in is failed with the encoding error like the following screenshot.

Workflow:

name: Azure Login Test

on:
  workflow_dispatch:

jobs:
  login:
    runs-on: windows-latest # using Windows runner
    steps:
    - uses: azure/login@v1
      with:
        creds: ${{ secrets.AZURE_CREDENTIALS }}

Error screenshot:

[horihiro]

Balaga Gayatri (@BALAGA-GAYATRI) could you please take a look at this or assign anyone?

[BALAGA-GAYATRI]

Hirofumi Horikawa (@horihiro) we shall look into this issue and let you know.

[horihiro]

Hello Balaga Gayatri (@BALAGA-GAYATRI)
I did addional check by the following job.

jobs:
  login:
    runs-on: windows-latest
    steps:
    - run: |
        az login --service-principal -u ${{ secrets.AZURE_CLIENT_ID }} -p ${{ secrets.AZURE_CLIENT_SECRET }} --tenant ${{ secrets.AZURE_TENANT_ID }}

Then, the job was succeeded, even though the same warning message WARNING: Unable to encode the output with cp1252 encoding. Unsupported characters are discarded. was shown.

From this result, it seems that the azure/login action and @action/exec module which is used in this action handle this warning as an error.
Could you please check this point?

[BALAGA-GAYATRI]

Sure. Will check this out and let you know. Thanks for the extra insights.

[BALAGA-GAYATRI]

Fixed this bug in v1.4.4 and updated azure/login@v1 with the latest release.