Determine if Office 365 PowerShell command was processed or accepted

Sometimes when typing in a command within Office 365 PowerShell it is hard to know if the PowerShell command was processed or accepted since the command will be typed and then enter is pressed but there is no output or visible result.

What are the best ways of determining if an Office 365 PowerShell command was successfully processed or accepted?

Is there an online event viewer or similar resource or tools that can be used?
IT GuyNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

timgreen7077Exchange EngineerCommented:
no unfortunately that is the nature of PowerShell.  you can use the  -whatif parameter at the end of your cmdlets, and this will show you what will happen when you execute the cmd, but but once you see what will happen you will need to remove the -whatif parameter in order to execute the cmd. whatif only shows what will happen but it doesn't actually execute the cmdlets. so no PowerShell doesn't show your results with a lot of cmdlets.
Most of the time, when powershell cmdlet returns no output, it means command is successful.

There is no verbose command you can check what happened in background while command is been executed

What you can do, you can user *get* cmdlets / commands to check / verify changed values for whatever you are trying to do is achieved

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
PowerShell cmdlets are throwing exceptions or writing out error or warning messages if there are issues.
If they just return with empty result, they did not hit any issue but just didn't get any result, e.g.  because of a filter condition not having any hits.
Some Set-* cmdlets do not return anything unless you provide -PassThru, which passes the changed object further down the pipeline for further processing.

The reasoning behind that is that cmdlets are supposed to run in a pipeline, where informational output would be disturbing.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.