-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Homepage on classes created with Moodle Integration gets redirected to default Homepage instead of Customized page that is set up in Tenant. #2734
Comments
We need to verify if anything from Moodle side is causing an issue. For example, The Plugins. Please Advise |
Following up to see if anyone had a chance to look at this thread yet. Awaiting Response! Thanks in Advance! -Priyanka |
Hi @PriyankaZEN First of all, I acknowledge that we see the same behaviour in our environment. We performed some investigation but didn't find the cause of the issue. So basically what happens is the "Home page" menu item in some class teams are pointing to the root URL of the SharePoint site for the tenant, while it should show the SharePoint site of the group of the team. The direct reason for this is - when a team (or rather class team in this case) is created, it should automatically create a SharePoint site. This should happen regardless of how the team is created, i.e. whether it's created from Teams web/desktop/mobile app, or from Graph API call. However, the SharePoint site creation site creation didn't happen for some reason, therefore there is not group SharePoint site URL to show. Teams seems to default to the tenant default SharePoint site in this case. I have tried to find out why the group SharePoint site creation action didn't happen when creating a class Team using Graph API call, but this seems to be a black box for me - it can only be looked at by the Microsoft team. I can provide details on the steps of how the class groups are created only, please try to escalate this inside Microsoft.
Note the steps above apply to tenants with education licences only, which is the case for OP and our development tenant. Also note there are additional steps after listed above to install Moodle app to Teams, add Teams app to channel etc, but they should be irrelevant to the Team creation itself. FYI, I did consider possible alternative solutions, e.g. force triggering a SharePoint site from group using Graph API after the group is created, however, the SharePoint Graph API feature doesn't support write actions, therefore this is infeasible. As said above, please escalate the issue inside Microsoft to find a solution. Please let us know if you need anything from our end in the investigation. References:
Regards, |
Thanks for a detailed description, Lai. I will take this up on our end.
Thanks and Regards,
Priyanka Metai
From: Lai Wei ***@***.***>
Sent: 22 January 2025 21:54
To: microsoft/o365-moodle ***@***.***>
Cc: Prriyankka Metai (ALLYIS INC) ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/o365-moodle] Homepage on classes created with Moodle Integration gets redirected to default Homepage instead of Customized page that is set up in Tenant. (Issue #2734)
Hi @PriyankaZEN<https://github.com/PriyankaZEN>
First of all, I acknowledge that we see the same behaviour in our environment. We performed some investigation but didn't find the cause of the issue.
So basically what happens is the "Home page" menu item in some class teams are pointing to the root URL of the SharePoint site for the tenant, while it should show the SharePoint site of the group of the team.
The direct reason for this is - when a team (or rather class team in this case) is created, it should automatically create a SharePoint site. This should happen regardless of how the team is created, i.e. whether it's created from Teams web/desktop/mobile app, or from Graph API call. However, the SharePoint site creation site creation didn't happen for some reason, therefore there is not group SharePoint site URL to show. Teams seems to default to the tenant default SharePoint site in this case.
I have tried to find out why the group SharePoint site creation action didn't happen when creating a class Team using Graph API call, but this seems to be a black box for me - it can only be looked at by the Microsoft team. I can provide details on the steps of how the class groups are created only, please try to escalate this inside Microsoft.
1. Call Create educationClass API<https://learn.microsoft.com/en-us/graph/api/educationroot-post-classes?view=graph-rest-beta&tabs=http> to create an education group.
2. Call Update group API<https://learn.microsoft.com/en-us/graph/api/group-update?view=graph-rest-1.0&tabs=http> to set microsoft_EducationClassLmsExt attributes.
3. Call Update group API<https://learn.microsoft.com/en-us/graph/api/group-update?view=graph-rest-1.0&tabs=http> to add initial owners and members to the group. Owners are added as members too in this step.
4. Call Create team API<https://learn.microsoft.com/en-us/graph/api/team-post?view=graph-rest-beta&tabs=http> to create a class team from the group (using ***@***.******@***.***> and ***@***.******@***.***> parameters).
Note the steps above apply to tenants with education licences only, which is the case for OP and our development tenant. Also note there are additional steps after listed above to install Moodle app to Teams, add Teams app to channel etc, but they should be irrelevant to the Team creation itself.
FYI, I did consider possible alternative solutions, e.g. force triggering a SharePoint site from group using Graph API after the group is created, however, the SharePoint Graph API feature doesn't support write actions, therefore this is infeasible.
As said above, please escalate the issue inside Microsoft to find a solution. Please let us know if you need anything from our end in the investigation.
References:
1. Discussion on Microsoft Tech Community about the same issue. https://techcommunity.microsoft.com/discussions/microsoftteams/team-creation-with-graph-api-not-creating-sharepoint-site/2037775/replies/2359910 I have verified the suggestions mentioned in the discussion (owner not being made as group member), but the Moodle integration is already doing it, therefore this doesn't solve the issue.
2. Document that describes SharePoint related features in Graph API. https://learn.microsoft.com/en-us/graph/api/resources/sharepoint?view=graph-rest-1.0
Regards,
Lai
-
Reply to this email directly, view it on GitHub<#2734 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A3VYYP7AGQJCL6JELFY4YAT2L7AY7AVCNFSM6AAAAABT3IZ5W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBXGY4TGMZUGU>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
• Issue is with all Classes created via integration.
• No issues with Teams/Classes that have been created directly from Teams Client.
• Customer has a NON-PROD environment where Teams T1 (Old Client) is being used and on integrated Teams/Classes, right Homepage appears.
• Issues seems to occur only on T21.
• Our SP Team has investigated the issue
• Same behaviour seen irrespective of class being activated or no.
Work Around being used as of now : Access integrated Teams on T1(Testing Environment). Once the Teams have been accessed on T1 once, Subsequent Access of Homepage on T21 works well (i.e Homepage seen would be the customized one, Not the Default Homepage)
Refer URL: https://judgebusinessschool.sharepoint.com/_layouts/15/brokerlogon.aspx?classhome=true&useTeamsAuth=true&dest=https://judgebusinessschool.sharepoint.com%3Fclasshome%3Dtrue&locale=en-gb
Moodle Details :
Moodle 4.3.8 (Build: 20241007)
Microsoft 365 Integration (local_o365) 4.3.6 (2023100925)
Correct home page link: https://judgebusinessschool.sharepoint.com/sites/202325_gmba14_learnjbs
landing page which is loading as home page: https://judgebusinessschool.sharepoint.com/
Unable to Attach HAR Files. Please share a file share link so I can attach HAR's
https://github.com/user-attachments/assets/c5cfd660-7be6-47ac-b69a-443fd1899d20
Fiddler Analysis by SP Team.txt
The text was updated successfully, but these errors were encountered: