To get the most out of this book
All you need is access to and licenses for the various apps and workloads in Microsoft 365, as well as the right administrative permissions. We’ll cover the specific requirements before each recipe. If you already have access to your organization’s Microsoft 365 subscription but are still unable to work your way through a recipe, you may need to reach out to your IT department to grant you the appropriate licenses and/or access required to complete the steps in that recipe.
Alternatively, you can also sign up for a Microsoft 365 trial account here: https://www.microsoft.com/en-us/microsoft-365/try. This will give you one month’s free access to a newly created Microsoft 365 environment. This option is recommended for organizations or users that want to try the service first. You will need to enter your billing information first, but you can cancel the subscription at any time.
Another option is to sign up for the developer program by visiting https://developer.microsoft.com/en-us/microsoft-365/dev-program. This will provide you access to a Microsoft 365 environment containing all the workloads and apps, with fictitious user accounts, along with a lot of dummy test content. This environment has a 90-day validity, after which it is deleted unless it is renewed. The developer program provides a great opportunity to learn about Microsoft 365 and its entire suite of apps.
Download the example code files
The code bundle for the book is also hosted on GitHub at https://packt.link/GitHub-repo. If there’s an update to the code, it will be updated on the existing GitHub repository.
We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!
Download the color images
We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: https://packt.link/gbp/9781803243177
Conventions used
There are a number of text conventions used throughout this book.
CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “Scaffold a web part template by typing yo @microsoft/sharepoint and respond to the questions that are asked.”
A block of code is set as follows:
Syntax:
Set(variable_name,value)
Any command-line input or output is written as follows:
npm install -g @microsoft/generator-sharepoint
Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in the text like this. Here is an example: “Click the Sync option in the header menu.”
Warnings or important notes appear like this.
Tips and tricks appear like this.
Sections
Like any cookbook, we’ve organized this book into a series of recipes that follow a regular structure. You will find several headings that appear frequently in the recipe format: Getting ready, How to do it..., How it works..., There’s more..., and See also.
To give clear instructions on how to complete a recipe, we’ve used these sections as follows.
Getting ready
This section tells you what to expect in the recipe and describes how to set up any software or any preliminary settings required for the recipe.
How to do it…
This section contains the steps required to follow the recipe. Don’t worry if you’ve got questions about some of the technical details; we’ll cover those in the next section.
How it works…
This section consists of a detailed explanation of what happened in the previous section. This helps to couple your practical skills with a deeper understanding.
There’s more…
This section consists of additional information, such as more advanced features for more niche situations.
See also
This section provides helpful links to other useful information for the recipe. This includes links to other resources as well as other relevant recipes elsewhere in this book.
