Moodle + Office 365: Better together


Provisioning an Office 365 environment



Download 345.09 Kb.
Page3/13
Date29.07.2017
Size345.09 Kb.
#24227
1   2   3   4   5   6   7   8   9   ...   13

Provisioning an Office 365 environment


As mentioned above, and by essence, an Office 365 subscription is required for the suggested test lab environment.

To sign up to a free 30-day Microsoft Office 365 Enterprise E3 trial, follow the instructions to the Office 365 Enterprise E3 trial version19.



Note For more information, see the article Sign in to Office 36520.

For the course of this walkthrough, we’ve provisioned an Office 365 Enterprise (E3) tenant: nfr123.onmicrosoft.com and created the vanity domain contoso123.fr underneath. You will have to choose instead of them domain names of your choice whose name is currently not in use. Whenever a reference to nfr123.onmicrosoft.com or contoso123.fr is made in a procedure, it has been replaced by the corresponding domain name of your choice to reflect accordingly the change in naming.



At this stage, we assume that you already have an active Office 365 subscription.

5.Creating the Office 365 accounts


To illustrate the Moodle with Office 365 integration, some Office 365 test users will be necessary. These users should have an Office 365 license assigned to access to the relevant Office 365 services.

The Moodle with Office 365 integration also requires an "System API" account with the appropriate privileges to sustains the requirements of the integration, in particular with SharePoint Online for the automatic creation of the collaborative workspaces for each Moodle course.

This section will cover how to create the test users, create the "System API" account, and grant this system account the adequate privileges on the SharePoint Online platform.

6.Creating the test users


For the purpose of our test lab environment, we will start by creating four test users: Teacher Martin, Student 1, Student 2 and Student 3, each with an Office 365 E3 license assigned to benefit from the Office 365 services.

To create the above test users, proceed with the following steps:



  1. Open a browsing session and navigate to the Office 365 management portal at https://portal.office.com.

  2. Sign in with an administration account of the Office 365 subscription.



  1. In admin shortcuts on the right of the user interface, click Add new users as highlighted above in yellow.



  1. On the details page, specify the user information that pertains to the account to create, and then click Next.



  1. On the settings page, fill in the additional information. The user must not be an Office 365 administrator. Set the appropriate location for the user depending on your geography, for example France in our illustration. Click Next.



  1. On the assign licenses page, select Office 365 Enterprise E3 as well as all the available option underneath, e.g. Office 365 ProPlus, Skype for Business Online, Office Online, etc. so that the user can use all the available Office 365 functionality. Click Next.



  1. On the send results in email page, type an e-mail address where the user will receive the password generated by the platform, for example “Teacher@contoso123.fr” in our illustration. Users can later change their password when they will sign-in for the first time. Click Create.

The user has now been created. The assigned password is displayed in results, so that you can potentially communicate it to the user by a mean other than e-mail if needed for some reasons.



  1. Click Create another user.

  2. Repeat steps 4 to 7 for the other users to be created. At the end of these operations, click Finish.

When using the Office 365 platform in a production environment, the accounts can be created automatically via identity management systems for example.

Moreover, it is also possible to use the same identities as the ones in your existing on-premises identity infrastructure, such as Active Directory for example, or another LDAP directory, using synchronization and single sign-on (a.k.a. federation) mechanisms if necessary.



Note The newly generally available Azure AD Connect tool can be used for that purpose for example. This is the one stop shop for connecting your on-premises directories to Azure AD, whether you are evaluating, piloting, or in production. Azure AD Connect provides a single and unified wizard that streamlines the overall onboarding process for both directory synchronization (single or multiple directories) AND single sign-on if you want to.

For additional information, see the Microsoft articles Integrating your on-premises identities with Azure Active Directory21 and Azure Active Directory Connect22.

These scenarios are not further covered in this paper.



Note For more information about these scenarios and their implementation in different types of environments, see the Azure AD/Office 365 Single Sign-On with AD FS in Windows Server 2012 R223 (Part 1 and Part 2bis) and Azure AD/Office 365 Single Sign-On with Shibboleth 224 whitepapers.

7.Creating the so-called "System API" account


Let's deal with the so-called "System API" account. You can call this account whatever you like. In our example, we are going to create the account moodleapi@contoso123.fr.

To create the account, follow the same procedure as the one illustrated in the previous section for the test users. However, in this case, please ensure that the administrator's privileges are granted to the account (on the settings page).

Do not allocate an Office 365 Enterprise E3 license to this account, since it does not need a mailbox nor the other Office 365 services.



Download 345.09 Kb.

Share with your friends:
1   2   3   4   5   6   7   8   9   ...   13



The database is protected by copyright ©ininet.org 2024
send message
    Main page
different types
latest version
latest information
same features
ongoing costs