Book Image

PowerShell for Office 365

By : Martin Machado
Book Image

PowerShell for Office 365

By: Martin Machado

Overview of this book

While most common administrative tasks are available via the Office 365 admin center, many IT professionals are unaware of the real power that is available to them below the surface. This book aims to educate readers on how learning PowerShell for Offi ce 365 can simplify repetitive and complex administrative tasks, and enable greater control than is available on the surface. The book starts by teaching readers how to access Offi ce 365 through PowerShell and then explains the PowerShell fundamentals required for automating Offi ce 365 tasks. You will then walk through common administrative cmdlets to manage accounts, licensing, and other scenarios such as automating the importing of multiple users,assigning licenses in Office 365, distribution groups, passwords, and so on. Using practical examples, you will learn to enhance your current functionality by working with Exchange Online, and SharePoint Online using PowerShell. Finally, the book will help you effectively manage complex and repetitive tasks (such as license and account management) and build productive reports. By the end of the book, you will have automated major repetitive tasks in Office 365 using PowerShell.
Table of Contents (16 chapters)
Title Page
About the Authors
About the Reviewer
Customer Feedback

Code signing

PowerShell's execution policy adds another layer of security to administrators. The default setting prevents executing scripts in order to be able to support automation, modules, or complex scripts. There are two other settings, that allow us to run scripts as long as they are signed.

Prevention of code execution is not the ultimate goal of these execution policy settings. A malicious agent may simply copy the remote script and execute it by copying and pasting the code in a PowerShell Terminal. The signed script's goal is to guarantee that the source of it is known and trusted and that the contents of the script code have not been tampered with.

Being able to validate the signature of a script allows some flexibility, such as being able to download scripts from a file share or web location. As long as the private key used to sign the scripts is kept safe by the author and the public key of the certificate is valid and remains trusted, the consumer can validate that the contents...