Azure Cloud Shell: Cannot type left parentheses

chrisw 81 Reputation points

Why can't I type a left parentheses in Cloud Shell?

When I type a Shift+9 (English keyboard) at the Cloud Shell prompt, the cursor stops blinking, becomes a hollow rectangle, and the Cloud Shell window loses mouse focus. No left parentheses appears on the screen. I've tried this in four different browsers and different computers - both PC and Mac - and with different logins. The behavior is the same in all cases - both in Bash and PowerShell. I don't experience this issue when typing any other characters.

What am I missing?

Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
651 questions
{count} votes

Accepted answer
  1. vipullag-MSFT 24,871 Reputation points


    Product team has rolled out fix for this bug and it will be live after 1st July.

    Hope this helps.

    Please 'Accept as answer' if it helped, so that it can help others in the community looking for help on similar topics.

    2 people found this answer helpful.

4 additional answers

Sort by: Most helpful
  1. Piotr Bienias 16 Reputation points

    I have exactly the same problem! The only solution I came up with, is to copy the "(" symbol to your clipboard, and then paste it in the shell whenever you need to type it.

    2 people found this answer helpful.

  2. Lukasz Sklariw 11 Reputation points

    It's not working for me as well..

    ALT 40 as a workaround

    2 people found this answer helpful.

  3. Micahl Dickens 6 Reputation points

    I am also experiencing this issue and it's preventing me from progressing in the course. Any solution?

    1 person found this answer helpful.
    0 comments No comments

  4. Tyler Woodward 1 Reputation point

    Had this issue today with the AZ-104 Azure PowerShell Module. Both left and right parentheses in the Cloud Shell function as described in the original issue. Using Firefox and Arch Linux.

    Copy and Paste continues to function as a valid work-around in the meantime.

    0 comments No comments