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
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

How to change the license for existing users


Before assigning licenses to users, it is good practice to check how many licenses are available unless you remember this information off the top of your head.

To check available licenses, we need to use following cmdlet:

Get-MSolAccountSku

This cmdlet will return the list of SKUs your organization/company owns. As you may have noticed, there is no required parameter for this cmdlet. An optional parameter is TenantId.

[-TenantId <Guid>] specifies the unique ID of the tenant.

By default, if the TenantId is not specified, the cmdlet will use the ID of the current user. TenantId is applicable for partner users (users who are registered partners and manage multiple tenants).

This cmdlet returns the AccountSku object, which contains the following information:

  • [AccountName]: The name of the account this SKU belongs to.
  • [AccountObjectId]: The unique ID of the account this SKU belongs to.
  • [AccountSkuId]: The unique string ID of the account/SKU combination...