how to get rid of the response from Exchange when password is invalid and catch error message instead?

Question

how to get rid of the response from Exchange when password is invalid and catch error message instead?

Konrad Wojciechowski (Nokia) 40

I have the following command:

$null = Connect-ExchangeOnline -Credential $cred -PSSessionOption $proxyOptions -ShowBanner:$false -ErrorAction Stop
SilentlyContinue -WarningAction SilentlyContinue -InformationAction SilentlyContinue -ErrorVariable authError 2> $null

if there is a credential error it prints me:

Error Acquiring Token:

AADSTS50126: Error validating credentials due to invalid username or password. Trace ID:

I want to get rid of this message from the screen as later I return some JSON output from this script and it ruins it. I've checked chatgpt and copilot for answers but without success so far.

I am using:

Import-Module -Name ExchangeOnlineManagement -RequiredVersion 3.1.0

Is there any way to do it?

Accepted answer

0 additional answers

Your answer

Answer 1

Rich Matheisen 47,901

Put a Clear-Host cmdlet after the Connect-ExchangeOnline cmdlet.

Errors are written to the error stream (STDERR). Have you tried redirecting that stream to the $null device on the Connect-ExchangeOnline cmdlet?

If there's a credential error, why not correct the credential and try again? What's the point of using the credential if you don't care if the cmdlet fails the authentication?

Anonymous

2024-09-26T08:21:40.4866667+00:00

Hello, @Konrad Wojciechowski (Nokia),

Welcome to the Microsoft Q&A platform!

Based on your description, I understand that you are encountering an issue with the Connect-ExchangeOnline command where an error message is being printed to the screen, disrupting your JSON output.

Rich Matheisen is right, you can first try to use the method he provided to deal with your problem, but Clear-Host Cmdlet can only help you to clear the information on the screen and not solve the error you are experiencing.

I suggest you verify your username and password based on the error message, correct the credentials and retry running the command. If you still encounter error messages, consider using Try and Catch blocks to catch any exceptions.For more information about the use of Try and Catch blocks, please click on about_Try_Catch_Finally - PowerShell | Microsoft Learn for reference.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Thank you for your support and understanding.

Best Wishes,

Alex Zhang
Konrad Wojciechowski (Nokia) 40 Reputation points

2024-09-26T11:11:24.06+00:00

I care. I just want to grab it in exception and return it in JSON format to the service.
Thanks a lot for your anwer with Clear-Host. I solved my issue. Thank you so much.
Rich Matheisen 47,901 Reputation points

2024-09-26T18:26:07.5766667+00:00

To get the exception you can wrap the Connect-ExchangeOnline in a try/catch. If the cmdlet throws an exception the exception object will be in the $_ variable when the "Catch" block is entered.
Konrad Wojciechowski (Nokia) 40 Reputation points

2024-09-27T11:00:17.8866667+00:00

@Rich Matheisen exception is easy to catch. However this message which shows - I cannot get rid of it...

Accoridng to this:
https://stackoverflow.com/questions/19163071/is-there-a-way-to-have-the-powershell-screen-clear-itself-before-each-command

"CLS, Clear and Clear-Host do not work when your powershell (or CMD for that matter) runs inside a PSEXEC session."

and this is exactly the situation I have - so proposed solution still does not work.

What I want to achieve is to connect through powershell to MS Exchange to add / remove SendAs or FullAccess rights to mailbox (as Graph API is not supporting this usecase). And when I have error in credentials I would like to return this message in JSON message to our automation. But this automatic text which appears in the screen (which I cannot get rid off...):

Error Acquiring Token:

AADSTS50126: Error validating credentials due to invalid username or password. Trace ID:

is ruining my output when credentials are not proper ...
Konrad Wojciechowski (Nokia) 40 Reputation points

2024-09-27T11:38:21.48+00:00

@Rich Matheisen exception is easy to catch. However this message which shows - I cannot get rid of it...

Accoridng to this:
https://stackoverflow.com/questions/19163071/is-there-a-way-to-have-the-powershell-screen-clear-itself-before-each-command

"CLS, Clear and Clear-Host do not work when your powershell (or CMD for that matter) runs inside a PSEXEC session."

and this is exactly the situation I have - so proposed solution still does not work.

What I want to achieve is to connect through powershell to MS Exchange to add / remove SendAs or FullAccess rights to mailbox (as Graph API is not supporting this usecase). And when I have error in credentials I would like to return this message in JSON message to our automation. But this automatic text which appears in the screen (which I cannot get rid off...):

Error Acquiring Token:

AADSTS50126: Error validating credentials due to invalid username or password. Trace ID:

is ruining my output when credentials are not proper ...
Konrad Wojciechowski (Nokia) 40 Reputation points

2024-09-27T11:39:26.0933333+00:00

Ok - i just removed this message in another system and as exception is handled properly - it is working fine. Thx for your answers and support.

Share via

how to get rid of the response from Exchange when password is invalid and catch error message instead?

0 additional answers

Your answer