Office 365 and Active Directory plugins for Moodle provide a more coherent and synchronous experience for teachers and students using both Moodle and Office 365. In order to be used, an Moodle administrator with Office 365 administrator privileges must configure the plugins for the Moodle site.
Although Moodle core now provides Office 365 authentication and basic OneDrive repository support, the Office 365 plugin suite provides a much wider set of features.
A few key features only found in the Office 365 plugin suite:
- User sync from Office 365/Azure AD to Moodle
- Automatic and manual user matching from Office 365/Azure AD to Moodle
- Calendar sync
- Course to Office 365 group sync and shared file repositories
- OneNote assignment submission and feedback types
- Office document embedding using Office web apps
- Fully customizable sign-in experience
To use the Office 365 plugins, you need the following:
- An Office 365 subscription.
- A Microsoft Azure subscription.
- Moodle version 3.1 or above.
Please note no paid Azure services are required to use the plugins. In particular, Azure Active Directory (also known as Azure AD or AAD) comes in three editions: Free, Basic, and Premium. The Free edition is all that is needed for use of the plugins. You can access the Azure Active Directory associated with your Office 365 tenant from the Office 365 Admin Settings.
The Office 365 set of plugins contains 5 core plugins, and 3 optional plugins, which provide a wide variety of features to enhance your Moodle instance.
- Office 365 Local Plugin (local_office365)
- This is a shell plugin which has dependencies on the current version of each of the 5 plugins that make up the complete set. Installing this plugin ensures you have the current version of each of the functional plugins installed.
- OpenID Connect Authentication Plugin (auth_oidc)
- This plugin allows users to log in to Moodle using their Office 365 accounts.
- Users with existing Moodle accounts can switch to using this authentication plugin, and new users can log in with this plugin and have an account created for them.
- If the administrator allows, users can also choose to disconnect from OpenID Connect and revert their previous login method, or to a username/password.
- Features
- Standards-Compliant OpenID Connect Authentication
- Supports authorization code or resource-owner credentials grants
- Users can log in to Moodle by clicking the identity provider on the login page, or by entering their OpenID Connect credentials.
- Customizable Icon + Identity Provider name
- The icon and identity provider name shown on the Moodle login page can be customized. A number of prechosen icons are available, as well as the ability to upload your own.
- Provides hooks to link OpenID Connect accounts to Moodle accounts
- If you do not want to change your users' login method, you can still connect to an OpenID Connect provider. The plugin provides code-level hooks to link a Moodle account to an OpenID Connect account without changing the Moodle user's authentication method. This means you can obtain tokens from an OpenID Connect service in the background.
- Optional user-self-service connection and disconnection
- A user-facing page is available for users to switch to and from OpenID Connect authentication. Access to this page and feature is controlled by a capability so administrators can disable it.
- Microsoft Block (block_microsoft)
- This block provides a user-facing menu to access various Office 365 integration features, resources, and settings.
- Links to Office 365 Resources associated with Moodle Courses (including Course SharePoint sites and Course Office 365 Groups) as well as a user's personal Office 365 Resources (including OneDrive for Business, Sways, Docs.com, Delve, Forms & OneNote Notebook).
- Contains Settings for settings such as Outlook Calendar sync preferences.
- Shows connection status to Office 365 and user photo from Outlook.
- Microsoft Office 365 Integration Local plugin (local_o365)
- This plugin provides most of the Office 365 integration back-end. This provides shared code to communicate with Office 365, and powers the calendar sync.
- Features
- Calendar sync from/to Office 365 Outlook.
- Users can sync site events, course events, assignment due dates, and their personal Moodle calendar to their Outlook calendar.
- User Sync and Matchign
- Users can be synced from Azure AD, or matched with existing users.
- Office 365 Groups for each Moodle course
- You can create Office 365 groups for each course in your Moodle instance (or you can select which courses are used). Links to Office 365 group resources such as Files, Conversations, and Calendar will be accessible from the Microsoft Block in each course. Moreover, the group files from each course group is accessible through the Office 365 repository. The group files is accessible by course teachers and students, serving as a place for teachers and students to share documents. Group membership is kept up-to-date with Moodle enrolments.
- SharePoint sites for each Moodle course (Deprecated)
- You can connect your Moodle instance to a SharePoint subsite. Sites below this will be created for each course in your Moodle instance, and the document library from each course subsite is accessible through the OneDrive for Business repository. The course subsite document library is accessible by course teachers, serving as a place for teachers to share documents.
- This feature is now deprecated. It is mainly used to provide shared document repositories for courses, which can now be accomplished by course groups.
- Calendar sync from/to Office 365 Outlook.
- OneDrive for Business Repository (repository_office 365)
- This is a repository plugin that allows users to access Office 365 resources in Office 365 services such as OneDrive for Business, SharePoint, and Office Video directly from the Moodle file-picker.
- Features:
- Import files into Moodle from Office 365.
- Upload files into Office 365 services from within Moodle.
- Link to resources in Office 365 so users always get the most up-to-date version.
- Embed Office 365 resources into Moodle courses so users can view them directly on the site.
These 3 plugins provide support for OneNote assignment submission and feedback. While they are not required, they provide a powerful way to submit and review assignments.
- OneNote support plugin (local_onenote)
- This provides supporting and shared code used by all other OneNote plugins. Does not have an user interface or configuration by itself.
- OneNote Assignment Feedback (assignfeedback_onenote)
- Allows teachers to leave feedback for students using OneNote.
- OneNote Assignment Submission (assignsubmission_onenote)
- Allows students to submit assignments using OneNote.
- oEmbed Filter (filter_oembed)
- This filter converts links to a variety of sites into oembed-powered interactions.
- Provides Office Mix support for Moodle, allowing you to embed Office Mixes directly into any text within Moodle.
Tooling and guidance on deploying Scalable Moodle Clusters on Azure
The packages are available from:
When you log back in to your Moodle instance, you are presented with the all the plugin configuration options. Save the settings without configuring them for now, you will come back to them later.
For information on installing plugins in Moodle see Installing plugins
After you have the plugins installed in your Moodle instance, you'll need to do a bit of setup before you can use and configure additional plugin settings including User Sync, SharePoint, etc. For more information on these additional settings see Microsoft Office 365 Integration Local plugin.
-
Navigate to Site Administration > Plugins > Authentication and click Manage authentication
-
Locate the OpenID Connect authentication plugin and click the eye icon to enable
-
Click the Settings link for the plugin.
-
Verify the Authorization and Token endpoints. These should be set by default but if not, set the endpoints to the following:
- Authorization Endpoint: https://login.microsoftonline.com/common/oauth2/authorize
- Token Endpoint: https://login.microsoftonline.com/common/oauth2/token
-
Note the Redirect URI. This should be the URI of your Moodle instance followed by /auth/oidc/. You will need to enter this value into Azure AD later, so note this value and put it aside.
- For example, https://www.example.com/auth/oidc/
- Notes:
- This is a fixed value that is derived from your Moodle site's configured URL (wwwroot). You cannot change this value directly. If you need to change it for any of the following reasons, you must change your Moodle site's configured domain name ($CFG->wwwroot).
- This URL must be a fully qualified domain name pointing to your Moodle instance.
- If your Moodle installation is configured with an IP address pointing to your instance, you must change $CFG->wwwroot in your config.php to a fully-qualified domain name.
- This domain name does not need to be publicly accessible (i.e. internet-wide), but does need to be accessible to users of your Moodle instance. So, for example, you can use a intranet-only domain name.
You will need an Azure subscription. If you do not have one, you can create one by visiting http://azure.microsoft.com/en-us/pricing/free-trial/ Microsoft Azure Sign Up
To use Moodle with Office 365 for SSO, you must configure Microsoft Azure to manage your Office 365 Microsoft Azure Active Directory:
- Create a new Active Directory.
- Select Use existing directory.
- Select I am ready to be signed out now and click the check mark.
- Sign in with your Office 365 subscription credentials.
- Click Continue.
- Log out and sign back in to your Azure account.
Note: In order to sign-up for an Azure subscription, you are required to enter a credit card and phone number. If only use the subscription to access the Azure Active Directory associated with your Office 365 subscription and enable no other paid services such as Virtual Machines, you will not be charged for the subscription.
- Sign in to the Microsoft Azure Management Portal.
- Click on the Azure Active Directory link on the left menu, then App Registrations.
- Click New application registration on the top menu.
- Enter a name for your application (can be anything you want, but should let you know this is for Moodle).
- Choose Web app/ API for the Application Type.
- The Sign-on URI is the Redirect URI you from the OpenID Connect authentication plugin configuration. Ensure there is a trailing slash for this URL - i.e. https://example.com/auth/oidc/
- Click Create.
- You now have an application registered in Azure for Moodle. Move on to the next section to properly configure it.
-
Sign in to the Microsoft Azure Management Portal.
-
Click on the Azure Active Directory link on the left menu, then App Registrations.
-
Click on the App you created for Moodle.
- You may need to change the dropdown from "My apps" to "All apps"
-
Locate the Application ID, note this value (write it down or copy it somewhere), and set it aside. You'll need it later.
-
Click on "Settings"
-
Create a client secret key.
- Click the Keys link, under "API Access".
- Enter a description, and select a duration for "Expires"
- Click Save
- A value will appear under Value, note this key value (write it down or copy it somewhere) and set it aside. You'll need later.
-
Configure Permissions
- Click the Required Permissions link under API Access.
- Click Add at the top of the pane.
- Click Select an API, choose "Microsoft Graph", then click Select.
- Click the checkbox for the following permissions in each of the "Application" and "Delegated" permissions sections:
| Type | Name | Use |
|---|---|---|
| Application Permissions | Read and write domains | Required to automatically detect your Office 365 tenant during setup. |
| Read and write all users' full profiles | Required to sync user information between Moodle and Office 365. | |
| Read and write all OneNote notebooks | Required for the OneNote integration to create notebooks, sections, and pages for assignments. | |
| Read and write all groups | Required for course group integration. | |
| Read directory data | Required for setup detection and verification. | |
| Read and write calendars in all mailboxes | Required for calendar event sync. | |
| Read and write files in all site collections | Required for the Office 365 repository to access, download, and upload files to OneDrive. | |
| Delegated Permissions | Read and write all OneNote notebooks that user can access | Required for the OneNote integration to create notebooks, sections, and pages for assignments. |
| Sign in and read user profile | Required to sign users in using Office 365, and to access Office 365 APIs. | |
| Read and write all users' full profiles | Required to sync user information between Moodle and Office 365. | |
| Read and write all groups | Required for course group integration. | |
| Read and write directory data | Required for setup detection and verification. | |
| Access directory as the signed in user | Required to access Office 365 APIs. | |
| Have full access to user calendars | Required for calendar event sync. | |
| Have full access to user files | Required for the Office 365 repository to access, download, and upload files to OneDrive. | |
| Read items in all site collections | Required for SharePoint integration (deprecated) | |
| Sign users in | Required to sign users in using Office 365 (required for all integration). |
When you're done, click save at the top of the screen.
-
Sign in to the Microsoft Azure Management Portal.
-
Click on the Azure Active Directory link on the left menu, then App Registrations.
-
Click on the App you created for Moodle.
- You may need to change the dropdown from "My apps" to "All apps"
-
Click the name of the app under Managed application in local directory
-
Click Users and groups under the Manage section.
-
Add users to your application using the Add user button.
The application will appear in the My apps page of the application launcher on the Office 365 portal for the users which have been assigned.
Navigate to Site Administration > Plugins > Local plugins. Click Microsoft Office 365 Integration. Under the Setup tab, complete each of the following steps:
-
Register Moodle and Azure AD (see above section)
- Copy the client ID and key from Azure AD into the appropriate fields.
- Click "Save changes" at the bottom of the screen.
-
Choose connection method
- Choose the method you want to use to connect to Office 365. Unless you have a special reason to use the System API user, choose Application access.
- Click Save changes
-
Admin consent & additional information
- Admin consent: Every time you change a Requires admin permission in Azure, you will need an administrator to provide consent to use the permission. Clicking the Provide admin consent button will take you to a log in screen on Office 365. An administrator will have to log in, and then will be given the option to approve the new permissions.
- Azure AD Tenant: This is the domain name that identifies your Office 365 subscription, for example "contoso.onmicrosoft.com". If you know it, enter it in this box, if not, click the "Detect" button to attempt to detect the correct value.
- OneDrive for Business URL: This is the URL that your users use to access OneDrive for Business. This can usually be determined from your AzureAD tenant, for example, if your tenant is "contoso.onmicrosoft.com", your OneDrive for Business URL is "contoso-my.sharepoint.com." If you know the URL, enter it here, otherwise click "Detect" to attempt to detect the correct value. Only enter the domain name, do not include "http://", "www." or any trailing slashes. For example "contoso-my.sharepoint.com", not "https://contoso-my.sharepoint.com/"
- Click Save changes.
-
Verify Setup
- This tool verifies that Azure has been correctly set up. Click the "Update" button to check setup.
- If the tool reports any missing permissions, return to Azure and ensure that all required permissions have been added to your configured application for Moodle.
To use any Office 365 features, a Moodle user must be connected to an Office 365 user that has an active Office 365 subscription. There are two ways to connect a Moodle user to an Office 365 user.
With this method, the user will log in to Moodle using their Office 365 account credentials.
- Users who do not yet have a Moodle account can simply follow the normal OpenID Connect login process (see: Office365#Basic_Usage). If a Moodle account is not found for a user logging in with OpenID Connect, an account will be created for them.
- To migrate an existing Moodle user to OpenID Connect authentication, see Office365#Switching_existing_Moodle_users_to_use_Office_365_to_log_in.
Users in Moodle can also be linked to Office 365 users without changing the Moodle user's authentication method. Users will be able to log in as they always have, and still use all the Office 365 features.
- Ensure the Microsoft block has been added to a page in Moodle (for example, the Moodle dashboard).
- As the user to link to Office 365, visit a page that has the Microsoft block visible.
- Click the Connect to Office 365 link in the Microsoft block.
- You will be brought to the Office 365 / Moodle Control Panel.
- There will be a "Connection Status" indicator box on the right side of the screen, click the "Click here to connect" link.
- You will be brought to the AzureAD authentication screen. Log in with the Office 365 user's credentials you'd like to connect to the Moodle user you are logged in as.
- If login was successful, you will be brought back to the Office 365 / Moodle Control Panel page, where the Office 365 connection indicator should now read Active.
- This user is now connected to the Office 365 user.
This plugin contains several configuration options and can be located under Site Administration > Plugins > Local plugins > Microsoft Office 365 Integration. It is organized into three tabs:
-
Setup. Configuration settings are outlined under the Setup section.
-
Options Contains various configuration options. Includes:
- User Sync
- Integration Settings
- Advanced Settings
-
Tools
- Health Check
- User Matching Tool
This controls how users are synced from Azure AD to Moodle. This can create or delete users in Moodle, match them with Azure Active Directory users, and assign them to Azure Active Directory applications.
The main benefit of using this option, compared to having accounts created as users log in using OpenID Connect, is that you can manage and enrol users before they first log in, so everything is ready to go the first time they access Moodle.
Users from Azure AD can be automatically created in Moodle using the user sync option. This creates a Moodle account for every user in the connected Active Directory allowing you to manage and enrol users in Moodle without the user having to log in first. When the user does log in using the OpenID Connect authentication plugin and their Office 365 account, they will be logged in to the account created for them during the user sync.
To enable:
- Check the checkbox beside each user sync option that you want to use.
- Click Save Changes.
- Run the Moodle cron to run the user sync process.
Notes:
- The sync job runs in the Moodle cron, and syncs 1000 users at a time.
- By default, this runs once per day at 1:00 AM in the time zone local to your server.
- To sync large sets of users more quickly, you can increase the frequency of the Sync users with Azure AD task using the Scheduled tasks management page. See Scheduled_tasks.
There are several options that affect user sync:
This will create users in Moodle from each user in the linked Azure Active Directory. Only users which do not currently have Moodle accounts will have accounts created. New accounts will be set up to use their Office 365 credentials to log in to Moodle (using the OpenID Connect authentication plugin), and will be able to use all the features of the Office 365 plugin set.
This will delete users from Moodle if they are marked as deleted in Azure AD. The Moodle account will be deleted and all associated user information will be removed from Moodle. Be careful!
This will look at the each user in the linked Azure Active Directory and try to match them with a user in Moodle. This looks for matching usernames in Azure AD and Moodle. Matches are case-insensitive and ignore the Office 365 tenant. For example, "BoB.SmiTh" in Moodle would match "[email protected]". Users who are matched will have their Moodle and Office accounts connected and will be able to use all Office 365/Moodle integration features. The user's authentication method will not change unless the setting below is enabled.
This requires the "Match" setting above to be enabled. When a user is matched, enabling this setting will switch their authentication method to OpenID Connect. They will then log in to Moodle with their Office 365 credentials. Note: Please ensure the OpenID Connect authentication plugin is enabled if you want to use this setting.
This will assign Azure AD users to the Moodle application in Azure. This will add the Moodle tile to the user's app launcher, and enable Moodle access if the "User assignment required to access app" setting is enabled in the Azure application.
This will sync users' profile photos into Moodle and set the Moodle user's profile photo to that image. Note that this can increase the time it takes to run user sync significantly.
If enabled, the user's Office 365 profile photo will be synced upon their log in to Moodle. This can be a more performant solution than (6) but users may experience a slightly delay in seeing profile photo updates.
During user sync, by default, all users from Azure AD will be created in Moodle. This setting allows you to set a required field and value that a user must have in Azure to have an account created in Moodle. For example, if you wanted to only have users from the "IT" department syncing into Moodle, you would choose the "Department" field, and enter "IT".
You can configure this setting to only sync users in an Office 365 "Office" group by choosing Office 365 Group Membership in the field select box. Type the exact name of the group in the "Field value" text box.
For other fields (anything but the group membership setting), you can also use regular expressions to match users. Choose the field you want to match against, and check the "Value is a regular expression" checkbox. Regular expressions allow you to specify patterns to match against. Read more about regular expressions at https://en.wikipedia.org/wiki/Regular_expression
This controls how information is synced from Azure AD to Moodle. The first column lists Azure fields, the second column lists Moodle fields, and the third column controls when information is synced. To create mappings:
- Click "Add Mapping"
- In the row that appears, select an Azure field to bring into Moodle.
- In the second column on the same row, select a Moodle field to copy the value into.
- In the third column on the same row, choose whether this only happens on user creation, on user login, or both.
- Click "Save Changes" at the bottom of the page.
To Delete A Mapping
- Click the "X" button at the end of the row you want to delete.
- Click "Save changes" at the bottom of the page.
- Note this will only prevent future information syncing, it will not undo past operations.
This section controls the various main features of the plugin suite, including what kind of Office 365 resources you want to create and associate with a Moodle Course. You have the option to create either a SharePoint subsite for your course and/or an Office 365 Group. Please Note If a SharePoint Site is not needed for your Course, and you are merely looking to have a SharePoint subsite for your course in order to have access to a document library accessible by all students and teachers associated with the course, it is recommended you enable only User Groups rather than the SharePoint connection.
User Groups (i.e. Office 365 groups) can be created for each course on your Moodle site giving users the ability to access Group resources such as Conversations, Group Files, and Calendar directly from the Microsoft Block via the Course Group link. The Group Files for each of these of these Office 365 groups can then be accessed by members using the Office 365 repository under "Groups (Courses)". Similar to the SharePoint link, this provides a shared store of files for a course, allowing students and teachers the ability to collaborate on documents and share resources.
Features:
- Once enabled, new groups will be created every cron run for any course that doesn't have an Office 365 group set up for it.
- Group membership is kept up-to-date with enrolments in Moodle.
- Provides an easy was to address all users in a course from Office 365. For example, a teacher can share a document from OneDrive with all of their students by choosing the user group for their course - they don't have to choose each student individually.
- Course group file stores are accessible from the Office 365 Moodle file repository plugin, allowing users to access group files from Moodle.
- By default the Office 365 group will be set as "Private" and the Moodle Admin will be set as an owner of the group.
- The Office 365 group Calendar is automatically synced with the Moodle Course calendar
Setting up User Groups (i.e. Office 365 groups)
- In the *User Groups* setting select from the following choices:
- Disable: This is the default setting. Leaving this box check will mean no Office 365 groups will be created.
- Custom: This allows you to select which Moodle courses for which you create a Moodle course and which group resources (i.e. Conversations, Group Files, Calendar etc.) are displayed in the Microsoft block. Once an Office 365 groups is created for a Moodle course, it is not deleted when a Course is unselected. Moreover, unselecting items such as Conversations, Group Files, etc. only remove links to those resources from the Microsoft block. They remain accessible from Office 365 for members of the group.
- All Features Enabled: This enables Office 365 groups for all Moodle courses and lists all group resources (i.e. Conversations, Group Files, Calendar, etc.) in the Microsoft block from the Course Group link.
This feature is deprecated and is likely to be removed in a future version.
SharePoint sites can be created for each course on your Moodle site. You will provide a parent SharePoint site and subsites for each course will be automatically created. The document library for each of these subsites can then be accessed by teachers using the Office 365 repository under "SharePoint (Courses)" . This provides a shared store of files for a course, allowing students and teachers the ability to collaborate on documents and share resources. In addition, this provides a SharePoint site that can be customized for the course and linked to from the Microsoft block. Note Any Azure AD connected Moodle user with the moodle/course:managefiles capability in a course will be able to access the document library from the repository.
Setting up the SharePoint connection
-
In the SharePoint Link setting, type in the URL of the parent SharePoint site you'd like to use for the course subsites. As you type, Moodle will verify the URL.
- This should be the entire URL to the SharePoint site - for example: <https://contoso.sharepoint.com/moodle>.
- This site must be accessible to the System API user
-
When you are done typing in the URL, the URL will be checked for suitability.
- If the valid is invalid, you will see a red box and the text "This is not a usable SharePoint site."
- If the site already exists, you will see a blue box and the text "This site is usable, but already exists". You can use this site, but conflicts can arise. It's recommended to use a URL to a SharePoint site that doesn't yet exist. The site will be created during initialization.
- If the site does not exist but can be created, you will see a green box and the text "This SharePoint site will be created by Moodle and used for Moodle content.". This SharePoint site will be created by Moodle during initialization.
-
Choose which courses you want to sync.
- Beneath the SharePoint link setting, you will see a "SharePoint course selection" setting. This allows you to choose which courses will have a SharePoint site created.
- "None" will not create any SharePoint sites.
- "Custom" will allow you to choose which courses have a SharePoint site created. A "customize" link will appear after you choose this link and click "Save changes".
- "Sync All" will create a SharePoint site for every Moodle course.
-
Click Save changes at the bottom of the settings page.
-
You will see a spinning icon below the SharePoint Link setting, and the text "Moodle is setting up this SharePoint site.". This will not automatically update - refresh the page to check if the connection has been set up.
-
The SharePoint Link is set up during the Moodle cron, so ensure your Moodle cron is set up and running.
Office 365 in China differs slightly in some technical aspects. If you are using Office 365 for China, select this box to ensure everything will work properly.
From time-to-time, we add features that use brand-new APIs or are slightly experimental in some way. These features often become part of our regular feature offering once they mature, but if you want to see the latest features we're working on, you can enable this setting to enable all preview features. Be careful though! These features do break from time to time.
If you experience problems using any Office 365 features in Moodle, enable this setting. Once enabled, errors will be recorded to the Moodle log for review. These errors can help you or the plugin developers debug and fix the problem. The error log can be viewed by navigating to Site Administation > Reports > Logs, changing the "All activities" select box to "Site errors", and clicking "Get these logs".
When using automatic user matching, this setting can be used to exclude accounts with short names. The intended use of this is to avoid matching generic accounts like "admin". This setting is the minimum length of a username required for automatic matching to match users.
The number of hours to wait before refreshing a user's profile photo.
This tool allows you to add additional Office 365 tenants to be used with Moodle. Users from additional tenants can log-in to Moodle using their Office 365 account, and use features like calendar sync and the OneDrive repository.
If you are experiencing problems with any Office 365 / Moodle features, click the Health Check link to run tests on your system and look for potential problems.
This tool allows administrators to see and manage the connections between their Moodle users and Office 365 accounts. Each user in the system is listed alongside the Office 365 username the user is connected to, if any. Administrators can choose to manually connect or disconnect each user.
This tool allows administrators to manually match Moodle and Office 365 users using a CSV file. Administrators can upload a CSV file containing, on each line, a Moodle username, and Office 365 username, and a 1 or 0 indicating whether to enable Office 365 login for that user.
Once uploaded, the file is processed in batches during the Moodle cron. The tool page will display the progress of this process.
These tools perform maintenance tasks that can help solve problems which may crop up from time to time. Generally, users should not need these tools unless they encounter the specific situation these tools are designed to solve.
Course group membership is kept up-to-date as users are enrolled and un-enrolled from courses in Moodle. If this membership gets out-of-date for whatever reason, this tool will force a resync of group membership.
Course groups are created from Moodle courses when using the course group feature. If a group is manually deleted from the Office 365 administrator panel, this tool will recreate it.
This tool will generate a package of information that can be sent to the plugin suite maintainers to help debug problems in environment and setup. While no API keys are present, this information does contain a lot about your environment and setup, so please be careful about who you send this information to.
This feature allows users to sync their Moodle calendars with Office 365. Users can have events in their Moodle calendar appear in any Office 365 calendar, and have events created in Office 365 synced back to Moodle.
To use this feature:
-
Ensure the Microsoft block has been added to a page in Moodle (for example, the Moodle dashboard).
-
As a user connected to Office 365, visit a page where the Microsoft block is visible.
-
Click the "Configure Outlook sync" link in the Microsoft block.
-
From here, you should see a list of your available Moodle calendars. Click the checkmark next to the ones you'd like to sync.
- By default, the calendars will sync with your Office 365 "primary" calendar. You can choose a different calendar to sync with using the "Sync with" select box.
-
You can also choose to sync from Office 365 in to Moodle (or both from Moodle to Office 365 and from Office 365 to Moodle). This is done using the "Sync behavior" select box.
-
Once you're subscribed to a calendar, wait for the site's cron function to run to sync older calendar events. However, new events should sync right away.
The Microsoft block provides the ability for users to quickly link off to Office 365 services.
- Course Group
- Course SharePoint site
- My Delve
- My Docs.com
- My OneNote Notebook
- My OneDrive
- Settings
- Outlook Calendar Sync settings
- Office 365 Connection settings
You can configure which of the following items show up in the plugins using the configuration settings under Site Administration \> Plugins \> Blocks \> Microsoft. A few important items to note:
- All settings besides Course Group and Course SharePoint site are evergreen, meaning they can be accessed at any time from any page on which the Microsoft block has been added to a page in Moodle
- If enabled, Course SharePoint site and Course Group only appear once the user is inside a Moodle course for which they are enrolled
- Course SharePoint site and Course Group cannot be disabled from the Microsoft block. They can only be enabled/disabled from the the Microsoft Office 365 Integration plugin.
This feature allows users to sync their Moodle calendars with Office 365. Users can have events in their Moodle calendar events appear in any Office 365 calendar, and have events created in Office 365 synced back to Moodle.
To use this feature:
-
Ensure the Microsoft block has been added to a page in Moodle (for example, the Moodle dashboard).
-
As a user connected to Office 365, visit a page where the Microsoft block is visible.
-
Click the "Outlook Calendar Sync settings" link in the Microsoft block.
-
From here, you should see a list of your available Moodle calendars. Click the checkmark next to the ones you'd like to sync.
- By default, the calendars will sync with your Office 365 "primary" calendar typically named "Calendar". You can choose a different calendar to sync with using the "Sync with" select box.
-
You can also choose to sync from Office 365 in to Moodle (or both from Moodle to Office 365 and from Office 365 to Moodle). This is done using the "Sync behavior" select box.
-
Once you're subscribed to a calendar, wait for the site's cron function to run to sync older calendar events. However, new events should sync right away.
Once configured, you should see a link named "OpenID Connect" on the Moodle login page. Clicking this link will redirect the browser to the identity provider. Users will log in there, and will be redirected back to Moodle. If they have logged in to Moodle using OpenID Connect before, they will be logged in to their existing Moodle account. If they have not logged in to Moodle with OpenID Connect before, an account will be created for them.
Note: If the "Prevent account creation when authenticating" setting is enabled in Moodle, new accounts will not be created.
There are a number of options you can use to customize how the plugin behaves. To configure the plugin, visit the plugin's settings page. (Site Administration > Plugins > Authentication > OpenID Connect)
The name entered here will be used through the OpenID Connect plugin and the Office 365 plugins to refer to the system used to log users in. For example, if your users are used to calling their Azure AD account their "School" account, you enter "School account" here, and all references to authentication will be "Log in with your School account".
Enter the Client ID obtained from Azure when you created the application for your Moodle installation.
Enter the Key obtained from Azure when you created the application for your Moodle installation.
You can use the default values for these.
You can use the default value for this.
When using the "Resource Owner Password Credentials" authentication method, this setting with automatically append a given string to an entered username. This is useful in Azure AD usernames, where a single domain name is often used for every user - i.e. [user]@contoso.onmicrosoft.com. Users would normally have to enter this entire username to successfully log in to Moodle, but in this example, entering "@contoso.onmicrosoft.com" here means users would only have to enter their unique username, i.e. "bob.smith", instead of "[email protected]".
If users have several different Azure AD accounts with different tenants (i.e. @contoso.onmicrosoft.com, @example.onmicrosoft.com), but Moodle only uses one of these tenants, you can enter that tenant in this box to have the Azure AD login screen only ever suggest accounts from that tenant.
This setting changes how users log in to Moodle using the plugin. You can redirect users to the OpenID Connect provider's login page, or have users enter their credentials directly into Moodle. See the "Authentication methods" section below for further information.
This setting allows you to restrict the users that can log in to Moodle using OpenID Connect (Azure AD).
Once you've entered at least one user restriction, users logging in to Moodle must match at least one entered pattern.
How to use user restrictions:
- Enter a regular expression pattern that matches the usernames of users you want to allow.
- Enter one pattern per line
- If you enter multiple patterns a user will be allowed if they match ANY of the patterns.
- The character "/" should be escaped with "\".
- If you don't enter any restrictions above, all users that can log in to the OpenID Connect provider will be accepted by Moodle.
- Any user that does not match any entered pattern(s) will be prevented from logging in using OpenID Connect.
If you experience problems using OpenID Connect, enable this setting. Once enabled, errors will be recorded to the Moodle log for review. These errors can help you or the plugin developers debug and fix the problem. The error log can be viewed by navigating to Site Administation > Reports > Logs, changing the "All activities" select box to "Site errors", and clicking "Get these logs".
This setting allows you to choose from a selection of predefined icons to appear next to the identity provider link on the login page. You can also upload your own icon.
- Visit the plugin settings page (Site Administration > Plugins > Authentication > OpenID Connect)
- Locate the "Icon" section of the settings page.
- There are several predefined icons to choose from, clicking an icon will use that icon on the login page.
- To use a custom icon, use the file picker below the "Icon" setting.
- This image will not be resized on the login page, so we recommend uploading an image no bigger than 35x35 pixels.
- If you have uploaded a custom icon and want to go back to one of the stock icons, click the custom icon in the file picker and click "Delete", then "OK", then "Save Changes" at the bottom of the settings page. The selected stock icon will now appear on the Moodle login page.
This plugin supports two different methods for users to log in: Authorization Code and Resource Owner Password Credentials Authentication
This method redirects the user to Office 365 to log in and are then brought back to Moodle logged in.
Using this method:
- The user clicks the name of the identity provider (What you entered in the "Provider Name" box at the top of the settings page.) on the Moodle login page.
- The user is redirected to Office 365 to log in.
- Once successfully logged in, the user is redirected back to Moodle where the Moodle login takes place transparently.
This method works like a classic username and password, except the user uses their Office 365 account information.
Using this method:
- The user enters their Office 365 username and password directly into the Moodle login form.
- Their credentials are securely sent to Office 365 for verification.
- If the credentials are verified, the user is logged in to Moodle.
If a user logs in to Moodle using OpenID Connect but does not have a Moodle account, one will be created for them. However, existing Moodle users can be migrated to use OpenID Connect and provide a connection to Office 365.
-
Ensure the Microsoft block has been added to a page in Moodle (for example, the Moodle dashboard).
-
Log in as the user to be migrated, visit a page that has the Microsoft block visible.
-
Click the Connect to Office 365 link in the Microsoft block.
-
You will be brought to the Office 365 / Moodle Control Panel.
-
Click the 'Office 365 Login link under Office 365 Features
-
Click the "Start using Office 365 to log in to Moodle." link.
-
You will be redirected to Office 365 to log in. Log in with the account you'd like to link to the Moodle account you're using.
- NOTE: If you're already logged in to Office 365, you will not have to enter your credentials on the Office 365 login page. This Office 365 account will be linked to the Moodle account. Ensure you are logged in to the correct account, or log out of Office 365 first to show the Office 365 login screen.
-
The Moodle account will now use Office 365 to log in. The previous login method will not work.
-
The Moodle user can now use any of the Office 365 features in Moodle.
-
Ensure the Microsoft block has been added to a page in Moodle (for example, the Moodle dashboard).
-
Log in as the user to be migrated, visit a page that has the Microsoft block visible.
-
Click the Connect to Office 365 link in the Microsoft block.
-
You will be brought to the Office 365 / Moodle Control Panel.
-
There will be a "Connection Status" indicator box on the right side of the screen, click the "Click here to connect" link.
-
You will be brought to the AzureAD authentication screen. Log in with the Office 365 user's credentials you'd like to connect to the Moodle user you are logged in as.
- NOTE: If you're already logged in to Office 365, you will not have to enter your credentials on the Office 365 login page. This Office 365 account will be linked to the Moodle account. Ensure you are logged in to the correct account, or log out of Office 365 first to show the Office 365 login screen.
-
If login was successful, you will be brought back to the Office 365 / Moodle Control Panel page, where the Office 365 connection indicator should now read Active.
-
The Moodle account is now linked to the Office 365 account and can use Office 365 features as that user.
-
The Moodle user's login method will not change, the user will log in to Moodle as they always have.
The Office 365 repository allows users using the Office 365 integration plugins to connect to various file stores within Office 365, including their personal OneDrive for Business, as a Moodle repository. You can configure which Office 365 services are available via the Moodle file-picker in the Office 365 repository settings page. Currently the services available are:
OneDrive contains all documents in your personal OneDrive for Business SharePoint (Courses) will list all SharePoint document libraries associated with Moodle Courses that you have access to. Group Files (Courses) will list all the Office 365 Group File folders associated with Moodle Courses that you have access to.
-
When using a file-picker anywhere in Moodle, you'll see a list of repositories on the left side of the popup. Look for and click on "Office 365".
-
If you are a regular user within Moodle, you will see folders for the services that have been enabled for you.
-
You will now see a list of all the files and folders in your OneDrive. If you want to download files from the "SharePoint (Courses)" or "Groups Files(Courses)", you'll click on the respective folder then click the folder for the course you want to access.
-
Navigate and click the file you want to download into Moodle.
-
Choose to "Make a copy of the file", or "Create an alias/shortcut to the file."
- If you want to download a copy of the file as it is now, choose "Make a cope of the file". This will copy the file into Moodle, and will then use the local Moodle copy when the file is accessed from within Moodle. Any changes to the file in OneDrive will not be seen in Moodle.
- If you want to link a file choose "Create an alias/shortcut to the file". This will create a link in Moodle to the file in OneDrive, and the file will be accessed from OneDrive directly. Any changes to the file in OneDrive will be seen when accessing the file from Moodle.
-
You can change other file information like the filename or author name using the respective text fields. This information is only applicable to the Moodle side of the file, and will not transfer to OneDrive.
-
Click "Select this file".
You can upload files into Office 365 from the Moodle file-picker interface.
- When accessing a Office 365 folder (for example, OneDrive) from a file picker, you will see an "Upload New File" item in the list of files and folders.
- Click the "Upload new file" item.
- Choose the file you want to upload and click "Upload this file".
- The file will be uploaded to OneDrive and selected for the file picker.
This repository allows users to embed Office documents from OneDrive into a course and have the live version viewable using Office web apps.
- Start as a user connected to Office 365 and who has access to modify a course.
- Turn on editing for the course and choose "Add an activity or resource" for the section of the course you want to add the document.
- Choose the "File" resource to add to the course.
- In the "Content" section of the file resource settings page, click the "Add" button in the filepicker
- Choose the "OneDrive for Business" repository and choose your Office document.
- When you select a file, make sure "Create an alias/shortcut to the file" is selected, the click "Select this file"
- Expand the "Appearance" section, and choose "Embed" for the "Display" select box.
- Click "Save and display"
- You should see the file embedded into the page.
If you have installed all the plugins (for example, by installing 1) then you already have the OneNote plugins installed. To access OneNote using your Office 365 subscription, add OneNote to the list of applications in your Azure application. This is done the same way you configured Azure permissions, above. Note that OneNote is still in preview, and may not be available to everyone yet. If you don't see OneNote in the list of applications to add to your Azure application, you can try logging in to a desktop OneNote application using an administrator account in your Office 365 tenant. This sometimes expedites to the process of adding the OneNote preview to your tenant.
Moodle will appear in a user's Office 365 app launcher if they are assigned to the application you created in Azure for Moodle. See the "Assign Users to your Azure Active Directory Application" section in setup. The integration local plugin also provides an option to automatically assign users to your Azure application. See "User Sync".
If the error is reproducible, enable the "Record debug messages" settings in both OpenID Connect and the integration local plugin (Site Administration > Plugins > Authentication > OpenID Connect, and Site Administration > Plugins > Local plugins > Microsoft Office 365 Integration > Options tab > Advanced settings). Reproduce the error with these settings enabled, and view your Moodle logs (Click the "View recorded log messages" link next to the Record debug messages setting in the integration local plugin). If you see an entry for Office 365, the log item may provide information on what went wrong. If the problem is not clear, please open an issue in our GitHub repository (https://github.com/Microsoft/o365-moodle) and we'll take a look at it.
The Microsoft block is not added to a Moodle page automatically. Once installed, navigate to the Moodle page you want to add the block to and click the "Customise this page" button. Look for the "Add a block" block and choose "Microsoft" from the dropdown. The Microsoft block will be added to the current page and can be managed like any other Moodle block.
Having trouble? Here are a few things to check, and how to proceed.
- Have you upgraded to the latest version of the plugins? Issues that encountered by others by already be fixed. Be sure to get the latest version of the plugins before anything else.
- Does your system meet the server minimum requirements? The plugins have the same minimum requirements as core Moodle. Please ensure your environment meets these requirements.
- Have you enabled the plugins you want? OpenID Connect and the Office 365 repository are not enabled by default. Be sure you have enabled these plugins through the Moodle administration interface.
- Are your permissions in Azure AD correct? From time to time these permissions may change. Check the Setup section of these docs to get the current list. You can also run the Azure AD Setup verification tool on the "Setup" tab of the local plugin settings page.
- Enable "Record debug messages" from the local plugin settings page then reproduce the error. The "View recorded log messages." link from the "Record debug messages" setting will show you any recorded logs. These often contain useful information that may point to the problem.
- Still having trouble? Submit an issue at https://github.com/Microsoft/o365-moodle/issues/. Please include:
- Your Moodle version
- The version of: auth_oidc, local_o365, repository_office365, and any other optional Office 365 plugins you have installed.
- Any debug messages recorded (see above). Thanks!
For support, please open an issue on Github at 2
For community discussion, please post in the Moodle office tool integrations forum on moodle.org. Note: developers may or may not see questions in this forum thread.
The Office 365 LTI integrations for Moodle do not require that you setup the Office 365 plugins to use and can be used independently or in conjucntion of the Office 365 plugins.
- Register your Moodle installation with Office Mix
- Go to https://mix.office.com/lti/.
- Click Register an LMS.
- If you are not already signed in, you will need to sign in with an appropriate account.
- Type a name to describe your Moodle installation.
- Select the checkbox indicating that you agree to allow Office Mix to pass data to your Moodle installation.
- Click Save.
- Make note of the Consumer Key, Shared Secret, and Launch URL that will be displayed on the page. You will need these in the subsequent steps below.
- To retrieve these at a later time, you can return to https://mix.office.com/lti/ and click Manage Your Registrations.
- Add Office Mix as an External Tool in Moodle
-
Log in to Moodle using your administrator account.
-
Go to Site Administration.
-
Go to Plugins > Activity modules > LTI > Manage external tool types.
-
Select Active.
-
Click Add external tool configuration.
-
In the Tool name box, type an appropriate name, such as "Office Mix".
-
In the Tool base URL box, enter the Launch URL obtained above.
-
In the Consumer key and Shared secret boxes, enter the values obtained above.
-
Check the "Show tool type when creating tool instances" checkbox.
-
Configure Privacy settings according to your requirements.
Note: Sending the Name of the user will allow Office Mix to display rich analytics and question responses. If you do not send any user information, then Office Mix will not be able restore a student's answers if they view the content on a subsequent visit.
-
Click Save changes.
Now that Office Mix has been configured, teachers or admins can follow the instructions in the next section to embed a Mix into course content:
-
Log in to Moodle as a Teacher or Admin.
-
Select the course you'd like to work with.
-
Click Turn editing on.
-
Locate the section that you'd like to modify and click Add an activity or resource.
-
Select External tool.
-
Click Add.
-
In the General settings:
-
In the Activity name box, type a name for your activity.
-
Select Office Mix from the External tool type list.
-
Set your Privacy and Grade settings.
-
Click Save and display. At this point, you should see a placeholder for your activity.
-
In the embedded activity, use one of these methods to select a mix:
-
Using URL: A simple way to select a mix is to visit the Office Mix website, select the mix you want to include in the course, copy the URL from the browser address bar and paste it in the dialog. This method makes it easy to include mixes that have been created by other people.
-
Using My Mixes: You can also select a mix from your My Mixes page from the Office Mix website. In order to prevent students from having to sign in to view a mix, only those mixes with permissions set to Unlisted or Public are shown.
-
-
After you have selected a mix, click Yes to confirm that this is the mix you'd like to use.
-
At this point, you should see the mix embedded within your course.
** Additional Resources** You may also refer to these Office Mixes for more information
- Register your Moodle installation with OneNote Class Notebook
- Go to https://www.onenote.com/lti.
- If you are not already signed in, you will need to sign in with an appropriate account.
- On the "Register Your LMS" page, enter a name to describe your Moodle installation.
- Click "Register".
- Make note of the Consumer Key, Shared Secret, and Launch URL that will be displayed on the page. You will need these in the subsequent steps below.
- To retrieve these at a later time, you can return to https://www.onenote.com/lti/ and click View/Manage Your Registration.
- Add OneNote Class Notebook as an External Tool in Moodle
- Log in to Moodle using your Moodle administrator account.
- Go to Site Administration.
- Go to Plugins > Activity modules > LTI > Manage external tool types.
- Select Active.
- Click Add external tool configuration.
- In the Tool name box, type an appropriate name, such as "OneNote Class Notebook".
- In the Tool base URL box, enter the Launch URL obtained above.
- In the Consumer key and Shared secret boxes, enter the values obtained above.
- Check the "Show tool type when creating tool instances" checkbox.
- Configure Privacy settings according to your requirements.
- Click Save changes.
Now that OneNote Class Notebook has been configured, teachers or admins can follow the instructions in the next section to embed a Class Notebook into course content by following the steps below:
- Log in to Moodle as a Teacher or Admin.
- Select the course you'd like to work with.
- Click Turn editing on.
- Locate the section that you'd like to modify and click Add an activity or resource.
- Select External tool.
- Click Add.
- In the General settings:
- In the Activity name box, type a name for your activity.
- Select "OneNote Class Notebook" from the External tool type list.
- Set your Privacy and Grade settings.
- Click Save and display. At this point, you should see a placeholder for your activity.
- At this point, you should see the Notebook embedded within your course.
- You will be guided through a sequence of dialogs to set up your notebook. Unless you want to change something, you can simply click Next on each one of them.
- At the end, a notebook will be added to your course.
Additional Resources You may also refer to this Office Mix presentation for more information: https://mix.office.com/watch/hg1qya375vxx
In order to use the Class Notebook Add-In for OneNote you must enable Office 365 web services.
- Enable web services.
- Go to
Site administration > Advanced features. Check the box next to "Enable webservices" and click "Save changes" - Enable the REST web services protocol
- Go to the web services "Manage protocols" page:
Site administration > Plugins > Web services > Manage protocols. - If the icon in the "Enable" column for the "REST protocol" row has a slash through it, click the icon to enable the protocol.
- Click Save changes
- Enable the "Microsoft Office 365 Webservices" service.
- Go to the web services "External services" page:
Site administration > Plugins > Web services > External services. - Find "Moodle Office 365 Webservices" in the "Built-in services" list, and click the "Edit" link in that row.
- Ensure the "Enabled" setting is checked (check it if it is not), and click "Save changes".
- Create a "webservices" role that allows users to use the REST webservice protocol.
- Go to the "Define roles" page:
Site administration > Users > Permissions > Define roles - Click "Add a new role"
- Choose "No role" for "Use role or archetype", click "Continue"
- Enter "rest_webservice_user" as the role short name, and "REST Webservice User" as the custom full name.
- Allow this role to be assigned at the system context.
- Search for
webservice/rest:usein the list of permissions, and check the "Allow" box in that row. - Scroll to the bottom of the page and click "Create this role"
- Assign each of the users you want to use the webservice this "REST Webservice User" role.
- Go to the "Assign system roles" page:
Site administration > Users > Permissions > Assign system roles. - Click the "REST Webservice User" link.
- Choose each user you want to assign from the right menu (you may have to search for each user individually), and click "Add" to assign them to the role.
- Create a token for each user you want to be able to use the webservice.
- Go to the web service "Manage tokens" page:
Site administration > Plugins > Web services > Manage tokens - Click the "Add" link.
- Choose the user you want to create a token for from the "User" list.
- Choose "Moodle Office 365 Webservices" from the "Service" list.
- Click "Save changes"
Now that webservices are set up on your Moodle site, you can begin making webservice calls.
All webservice calls:
- are POST requests made to
[moodle]/webservice/rest/server.php - use URL encoded parameters in the body of the post request.
- require (at minimum) three parameters:
wstokenThis is the token you created for the user in the "setup" section above.wsfunctionThis is the name of the function you are calling.moodlewsrestformatThis is the format you expect the response in, we will use "json"
For example, a request to get a list of a teacher's courses:
POST http://example.com/webservice/rest/server.php
Content-Type: application/x-www-form-urlencoded
wstoken=309ada75ccb5518f368d103b3c1fb0cb&wsfunction=local_o365_get_teachercourses&moodlewsrestformat=json
This function gets a list of courses that the requesting user is a teacher in. "Teacher" in this case is defined as a user with the moodle/grade:edit capability.
Function: local_o365_get_teachercourses
Parameters: none
Response: array of objects, each containing:
idint The course ID.shortnamestring The shortname of the course.fullnamestring The full name of the course.idnumberstring The course ID number.visibleint Whether the course is visible. 1 or 0, 1 being visible, 0 being hidden.formatstring The course format.showgradesint Whether grades are shown.langstring The course language.enablecompletionint Whether completion is enabled.
This function gets a list of user enrolled in a given course. This will only return information for courses the requesting user can access.
Function: local_o365_get_course_users
Parameters:
courseidint The ID of the course
Response: array of objects, each containing:
idint The user's ID.fullnamestring The user's full name.firstnamestring The user's first name.lastnamestring The user's last name.emailstring The user's email address.profileimageurlsmallstring A URL to a small version of the user's profile photo.profileimageurlstring A URL to the user's profile photo.
This function will create a new OneNote assignment in a given course.
Function: local_o365_create_onenoteassignment
Parameters:
dataarray An wrapper array containing:namestring The name of the assignment.courseint The ID of the course to create the assignment in.introstring (Optional) A description of the assignment. Default is an empty string.sectionint The ID of the course section to create the assignment in.visibleint (Optional) Whether to make the assignment visible or hidden. 1 to make visible, 0 to make hidden. Default is 0 (hidden).
Response:
dataarray Array of objects, each containing:courseint The ID of the course the assignment was created in.coursemoduleint The course module ID.instanceint The assignment ID.namestring The name of the created assignment.introstring The description of the created assignment.sectionstring The ID of the course section the assignment was created in.visibleint Whether the assignment is visible or hidden. 1 = visible, 0 = hidden.
This function will return information about a OneNote assignment given a course module ID and course ID.
Function: local_o365_get_onenoteassignment
Parameters:
dataarray An wrapper array containing:coursemoduleint The course module ID.courseint The ID of the course the assignment is in.
Response:
dataarray Array of objects, each containing:courseint The ID of the course the assignment is in.coursemoduleint The course module ID.instanceint The assignment ID.namestring The name of the assignment.introstring The description of the assignment.sectionstring The ID of the course section the assignment is in.visibleint Whether the assignment is visible or hidden. 1 = visible, 0 = hidden.
This function will allow you to update various attributes of a OneNote assignment.
Function: local_o365_get_onenoteassignment
Parameters:
dataarray An wrapper array containing:coursemoduleint The course module ID.courseint The ID of the course the assignment is in.namestring (Optional) The new assignment name to set.introstring (Optional) The new description to set.sectionstring (Optional) The ID of the course section to move the assignment to.visibleint (Optional) The assignment's new visibility status. 1 = visible, 0 = hidden.
Response:
dataarray Array of objects, each containing:courseint The ID of the course the assignment is in.coursemoduleint The course module ID.instanceint The assignment ID.namestring The name of the assignment.introstring The description of the assignment.sectionstring The ID of the course section the assignment is in.visibleint Whether the assignment is visible or hidden. 1 = visible, 0 = hidden.
This function will allow you to remove a OneNote assignment.
Function: local_o365_delete_onenoteassignment
Parameters:
dataarray An wrapper array containing:coursemoduleint The course module ID.courseint The ID of the course the assignment is in.
Response:
resultbool Whether the operation was successful (true), or not (false).
- Get a list of the teacher's courses
Request:
POST https://example.com/webservice/rest/server.php
Content-Type: application/x-www-form-urlencoded
wstoken=309ada75ccb5518f368d103b3c1fb0cb&wsfunction=local_o365_get_teachercourses&moodlewsrestformat=json
Response:
[
{
"id":3,
"shortname":"PSYCH102",
"fullname":"Introductory Psychology 2",
"idnumber":"",
"visible":1,
"format":"weeks",
"showgrades":true,
"lang":"",
"enablecompletion":false
},
{
"id":2,
"shortname":"PSYCH101",
"fullname":"Introductory Psychology 1",
"idnumber":"",
"visible":1,
"format":"weeks",
"showgrades":true,
"lang":"",
"enablecompletion":false
}
]
- Get a list of users for PSYCH101.
This uses the 'id' parameter for the PSYCH101 course returned above as the 'courseid' parameter.
Request:
POST https://example.com/webservice/rest/server.php
Content-Type: application/x-www-form-urlencoded
wstoken=309ada75ccb5518f368d103b3c1fb0cb&wsfunction=local_o365_get_course_users&moodlewsrestformat=json&courseid=2
Response:
[
{
"id":175,
"fullname":"John Smith",
"firstname":"John",
"lastname":"Smith",
"email":"[email protected]",
"profileimageurlsmall":"http:\/\/example.com\/theme\/image.php\/clean\/core\/1459671559\/u\/f2",
"profileimageurl":"http:\/\/example.com\/theme\/image.php\/clean\/core\/1459671559\/u\/f1"
},
{
"id":176,
"fullname":"Jane Smith",
"firstname":"Jane",
"lastname":"Smith",
"email":"[email protected]",
"profileimageurlsmall":"http:\/\/example.com\/pluginfile.php\/24\/user\/icon\/clean\/f2?rev=469",
"profileimageurl":"http:\/\/example.com\/pluginfile.php\/24\/user\/icon\/clean\/f1?rev=469"
},
]
- Get a list of assignments for PSYCH101
This uses the 'id' parameter for the PSYCH101 course returned in step 1 as the sole item in the 'courseids' parameter.
Request:
POST https://example.com/webservice/rest/server.php
Content-Type: application/x-www-form-urlencoded
wstoken=309ada75ccb5518f368d103b3c1fb0cb&wsfunction=mod_assign_get_assignments&moodlewsrestformat=json&courseids%5B%5D=2
Response:
{
"courses":[
{
"id":2,
"fullname":"Introductory Psychology",
"shortname":"PSYCH101",
"timemodified":1450214936,
"assignments":[
{
"id":1,
"cmid":2,
"course":2,
"name":"OneNote Test Assignment",
"nosubmissions":0,
"submissiondrafts":0,
"sendnotifications":0,
"sendlatenotifications":0,
"sendstudentnotifications":1,
"duedate":0,
"allowsubmissionsfromdate":0,
"grade":100,
"timemodified":1447960195,
"completionsubmit":0,
"cutoffdate":0,
"teamsubmission":0,
"requireallteammemberssubmit":0,
"teamsubmissiongroupingid":0,
"blindmarking":0,
"revealidentities":0,
"attemptreopenmethod":"none",
"maxattempts":-1,
"markingworkflow":0,
"markingallocation":0,
"requiresubmissionstatement":0,
"configs":[
{
"id":1,
"assignment":1,
"plugin":"file",
"subtype":"assignsubmission",
"name":"enabled",
"value":"0"
},
{
"id":2,
"assignment":1,
"plugin":"onlinetext",
"subtype":"assignsubmission",
"name":"enabled",
"value":"0"
},
{
"id":3,
"assignment":1,
"plugin":"onenote",
"subtype":"assignsubmission",
"name":"enabled",
"value":"1"
},
...
]
"intro":"",
"introformat":1
}
]
}
]
}
- Get existing grades for the "OneNote Test Assignment" in PSYCH101.
This uses the 'id' parameter from the assignment we want from the 'assignments' object returned in the above step as the sole item in the 'assignmentids' parameter.
Request:
POST https://example.com/webservice/rest/server.php
Content-Type: application/x-www-form-urlencoded
wstoken=309ada75ccb5518f368d103b3c1fb0cb&wsfunction=mod_assign_get_grades&moodlewsrestformat=json&assignmentids%5B%5D=1
Response:
{
"assignments":[
{
"assignmentid":1,
"grades":[
{
"id":3,
"userid":175,
"attemptnumber":0,
"timecreated":1459661701,
"timemodified":1459662202,
"grader":3,
"grade":"88.00000"
}
]
}
],
"warnings":[]
}
We can see here there is one grade present for this assignment, from user "John Smith" (ID 175 from step 2). 5. Create a new grade entry
This request uses the assignment id found in step 3, the user id from step 2 and a the new grade to set.
Request:
POST https://example.com/webservice/rest/server.php
Content-Type: application/x-www-form-urlencoded
wstoken=309ada75ccb5518f368d103b3c1fb0cb&wsfunction=local_o365_update_grade&moodlewsrestformat=json&assignmentid=1&userid=175&grade=78&attemptnumber=-1&addattempt=0&workflowstate=&applytoall=1&plugindata%5Bassignfeedbackcomments_editor%5D%5Btext%5D=&plugindata%5Bassignfeedbackcomments_editor%5D%5Bformat%5D=2&plugindata%5Bfiles_filemanager%5D=0
This function should return null if it was successful. You can repeat step 4 to verify the grade was saved correctly.
- Create a new OneNote assignment
This will create a new assignment in a given course, with the OneNote assignment and feedback types enabled.
Request:
POST https://example.com/webservice/rest/server.php
Content-Type: application/x-www-form-urlencoded
wstoken=309ada75ccb5518f368d103b3c1fb0cb&wsfunction=local_o365_create_onenoteassignment&moodlewsrestformat=json&data%5Bname%5D=A+new+test+onenote+assignment&data%5Bcourse%5D=2
Response:
{
"data":[
{
"course":2,
"coursemodule":91,
"name":"A new test onenote assignment",
"intro":"",
"section":1,
"visible":0,
"instance":49
}
]
}
Note that the "assignment id" referenced above for use with the grade-related functions is the "instance" attribute returned here. The "coursemodule" attribute is used with the other OneNote assignment functions (along with the course id) to get, update, or delete the assignment.
This filter allows users to embed documents from various online sources to be embedded into Moodle content. The user only has to enter the URL to the document and the filter takes care of converting the URL into an embeddable IFRAME. This filter has a white list of services it supports. The list of supported services can be seen and selectively enabled or disabled in the settings page for this filter.
This filter allows users to embed Power BI items into a course.
-
If you have upgraded filter plugin recently, clear the Moodle cache first then go to filter plugin settings and esure that the PowerBI filter is enabled.
-
In the Azure Portal (https://manage.windowsazure.com) go to your AD application, then inside 'Permissions to other applications' click Add Application.
-
Select Power BI Service, save, then set Delegated permissions as follows:
- View all reports(preview)
- Read and Write all Datasets
- View all Datasets
- View all Dashboards(preview)
-
Click on Save
-
Login to Office 365 and go to the Power BI app.
-
The menu on the left hand side contains the Reports section. Select the report you want to embed. (Note that the filter only works for Reports, not for Tiles.)
-
Copy the URL & paste it into Moodle content where you would like to embed the report.
-
Save the Moodle content and view it. You should see the URL you entered get converted into an IFRAME with the report showing inside it.
Setting up a Moodle Dev Test with the Office 365 plugins in Azure using Azure Resource Manager Templates
This document describes how to deploy Moodle and the Office 365 plugins quickly and easily on Microsoft Azure using an Azure Resource Manager (ARM) template. Azure Resource Manager (ARM) templates are declarative templates written in JSON that can be used to quickly create entire deployments consisting of VM's, databases, load balancers, network configuration etc. Please note that you need to have an Azure subscription to create these deployments. If you don't already have a subscription, you can get a free trial subscription here: https://azure.microsoft.com/en-us/pricing/free-trial/
- Go to the appropriate template on Github:
- To create a single VM deployment on Ubuntu, go to https://github.com/Azure/azure-quickstart-templates/tree/master/moodle-singlevm-ubuntu
- To create a clustered deployment on Ubuntu, go to https://github.com/Azure/azure-quickstart-templates/tree/master/moodle-cluster-ubuntu
- The readme describes the layout of the deployment that will be created and additional services you can set up after the deployment is done.
- Click on the "Deploy to Azure" button in the readme
- This will take you to the Azure portal with the template ready to be customized and deployed.
- You will need to enter the required parameters, specify a resource group, accept the legal terms, and start your deployment.
- When the deployment is complete, your Moodle instance will already be set up with the Office 365 plugins (if selected).
While Moodle requires each plugin to be it's own repository, developing a set of dependant plugins can be made easier by using a single repository for all plugins and overlaying the repository on top of a Moodle repository. In this setup, two repositories live in the same directory using two different .git directories – usually .git and .mdlgit. Using repository-specific gitignore rules, each repository deals with it's own files – allowing you to manage files, change branches, and view status independently.
- Clone Moodle into a new directory (or use a clean existing site), and check out the branch you'll be using.
git clone [repository] [directoryname] - Change directories to the cloned site
- Check out the branch you'll be using.
git checkout -t -b MOODLE_35_STABLE origin/MOODLE_35_STABLE - Rename the .git directory to .mdlgit
- Clone the development repository into a bare repository within the checked out Moodle code git clone --bare [repository] .git
- Add gitignore rules.
- Note: In a .git directory, repository-specific gitignore rules can be placed in info/exclude. Note that these rules will not be committed to the repository, so must be manually added for each new clone.
- Add the following to .git/info/exclude:
** !auth !auth/oidc !auth/oidc/** !blocks !blocks/microsoft !blocks/microsoft/** !filter !filter/oembed !filter/oembed/** !local !local/o365 !local/o365/** !local/office365 !local/office365/** !local/onenote !local/onenote/** !mod !mod/assign !mod/assign/feedback !mod/assign/feedback/onenote !mod/assign/feedback/onenote/** !mod/assign/submission !mod/assign/submission/onenote !mod/assign/submission/onenote/** !repository !repository/office365 !repository/office365/**- Add the following to .mdlgit/info/exclude.
.mdlgit auth/oidc blocks/microsoft filter/oembed local/o365 local/office365 local/onenote mod/assign/feedback/onenote mod/assign/submission/onenote repository/office365 - Manually change the development repository into a normal repository
git config core.bare false git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*" git fetch git checkout [branch] - Check status
git status git --git-dir=.mdlgit status
- All changes must adhere to the Moodle coding style.
- All changes must pass a peer-review by a maintainer.
- Use the short-array syntax - [] instead of array()
- All files must have the standard Moodle copyright notice at the top.
// This file is part of Moodle - http://moodle.org/
//
// Moodle is free software: you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// Moodle is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with Moodle. If not, see <http://www.gnu.org/licenses/>.- All files must have a package, author, license, and copyright line.
/**
* @package local_o365
* @author James McQuillan <[email protected]>
* @license http://www.gnu.org/copyleft/gpl.html GNU GPL v3 or later
* @copyright (C) 2014 onwards Microsoft Open Technologies, Inc. (http://msopentech.com/)
*/- The package must be the component name of the plugin the file is part of - local_o365, repository_office365, etc.
- The author line must be your full name and company email address.
- The license must be a GPLv3 or later line, shown above.
- The copyright line must be "[year] onwards Microsoft Open Technologies, Inc.", shown above.
- All classes must have a doc block, explaining the purpose of the class.
- All methods must have a complete doc block explaining the purpose of the method, all parameters, and return values.
- All class properties must have a short doc block explaining the property type and the property's purpose.
Ex.
/** @var \local_o365\httpclientinterface An HTTP client to use for communication. */
All new classes must be autoloadable and placed in the classes directory of the plugin. No exceptions.
- All API calls must have their responses validated, with any errors logged. For classes that extend \local_o365\rest\o365api, you can use $this->process_apicall_response, which will detect standard error responses and allow you to specify required keys and values.
- Use existing classes to manage and access tokens, http requests, and client data. They handle things like token refreshing, tokens for new resources, and http request quirks automatically.
- Plugin code generally doesn't access the rest API classes directly, but calls higher-level functions in feature classes. These are located in classes\feature. This allows the underlying API to be switched out by only modifying the feature class. This is not a strict rule but should be done whenever possible.
- When making an API call and fetching the token with \local_o365\oauth2\token::instance or \local_o365\oauth2\systemtoken::instance, check that you actually received a token object. This function will return null if it could not get a token for the specified user/resource, and this often happens when the plugins have not yet been configured, or configured incorrectly. \local_o365\oauth2\clientdata::instance_from_oidc is a time-saving function that will construct a clientdata object from the configured values in auth_oidc. You should use this to keep code simple and ensure a proper object is constructed. However, it will throw an exception if auth_oidc is not configured, so your code needs to expect and handle that.
- Feature Classes/Namespaces
- Plugin features, ex. Calendar sync, user sync, and user group creation, must be organized into "feature" namespaces within the \local_o365\feature namespace. Everything specific to a feature incl. event handlers, tasks, page classes, and general code must live somewhere within the feature namespace. This keeps feature-specific mode centralized and modular.
- "Features" often have "main" classes that are functionality abstractions that live between the main plugin code and the API classes. This is mainly done to gracefully handle API changes like the Graph API migration, but also keeps specific actions centralized and standardized.
- Main plugin code, i.e. user/admin control panel pages, must call a feature class instead of a specific API class. If we need to change the underlying API or change how an API call is handled, we can just update the feature class and not every API call.
- API Classes
- All classes that call Office 365 APIs must live in the \local_o365\rest namespace. These must extend \local_o365\rest\o365api.
- All JSON API responses must be run through $this->process_apicall_response. This will check for error responses, and optional defined structure, and do required logging.
- Utility Class
- \local_o365\utils provides a number of useful functions to perform common tasks in a standardized way.
- is_configured() - This determines whether the plugins are configured and active. Any plugin code that could run when the plugins are not configured, ex. event handlers and tasks, must use this function to check whether the plugins are configured and, if not, exit early before attempting any work.
- is_o365_connected() - Performs a number of checks to determine whether a user is connected to Office 365. This should be used to check whether to perform plugin-specific tasks for a user, ex. in event handlers and tasks.
- \local_o365\utils provides a number of useful functions to perform common tasks in a standardized way.
- Page Classes
- Any user-facing interface must use page classes, extending the \local_o365\page\base class.
- Page classes implement different views in "mode" functions within the class and are then run by instantiating the page class and running $page->run($mode).
- For example, if you run $page->run('calendar') the page class will run mode_calendar(). There is also a general "header()" function you can implement to run general page setup tasks. See \local_o365\page\ajax and \local_o365\page\ucp for examples of implemented page classes, and /local/o365/ajax.php and /local/o365/ucp.php for example of how to run a page class.
- All upgrade steps must be able to be run more than once without damaging data. They should be written in a way to check whether the upgrade is needed, or to check for old data when migrating data. Remember that all upgrade steps will be run again when a user moves major Moodle versions - 2.7 to 2.8 for example, so be prepared!
- Use db_manager functions like table_exists, field_exists, index_exists.
- Check for existing values when setting default values.