Loop and GitHub

Hi @Silletta Francesco,

Welcome to the Microsoft Q&A forum.

Normally, when you add /github to Microsoft Loop, the system displays a dialog box with the “Proceed” option, as shown in the illustration below.

However, based on the image you provided and the results from the test environment that I performed, it appears that this dialog does not appear or is interrupted at the Proceed step, which prevents the setup process from continuing.

In this case, I recommend that you create a support ticket with Microsoft Technical Support so the issue can be reviewed and analyzed in more detail.

How to create a support ticket

Note: The steps below require a Global Administrator account. If you do not have this permission, please contact your organization’s IT department for assistance.

Step 1: Go to admin.microsoft.com

Step 2: Select Help & Support

Step 3: Enter the ticket title, for example:

Request assistance to investigate Microsoft Loop

Step 4: Select Contact Support

Step 5: Choose your preferred contact method (chat or email)

After the ticket is submitted and assigned to a support agent, Microsoft will proactively contact you to provide assistance.

Additional note: If you submit the ticket over the weekend, the support agent may contact you at the beginning of the next business week.

 If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.

I look forward to continuing the conversation.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

The GitHub integration dialog in Loop should display a Proceed/Continue button as part of the GitHub app flow. If the button is missing and the prompt cannot be executed, this is typically caused by configuration or policy restrictions rather than a UI issue.

Based on the documented behavior:

1. When typing / and selecting GitHub from the Apps menu, Loop opens a GitHub integration dialog where the user must select Proceed and then sign in with GitHub credentials.
2. If tenant or privacy settings block external integrations, the experience may not complete and can appear as if there is no actionable button.

To resolve this:

1. Check Optional Connected Experiences (OCE) in Loop
   • In the Loop web app, open the three-dot menu (settings).
   • Ensure Optional Connected Experience is enabled.
   • If this setting is managed by the organization, contact the IT admin to enable it.
2. Verify admin policies for external data integrations
   Tenant admins can control Loop’s external integrations (including GitHub) via Cloud Policy:
   • Ensure the policy Import, view, and edit, items from apps integrated with Loop is Enabled or Not Configured.
   • Ensure the specific policy Import, view, and edit, GitHub items from Loop is also Enabled or Not Configured.
   • If these policies are Disabled, GitHub data will not synchronize and existing or new connections become read-only, which can prevent the Continue/Proceed action from appearing or working.
3. Confirm account type
   • GitHub integration in Loop is not available for Microsoft consumer (MSA) accounts.
   • Sign in with a work or school account associated with Microsoft 365 for business.
4. Check for admin blocking of 3rd-party integrations
   • If the admin console blocks 2P (third-party) integrations, GitHub cannot be fully enabled.
   • Contact the GitHub or Microsoft 365 admin to allow the GitHub integration for Loop.

Once Optional Connected Experiences and the relevant Loop data-integration policies are enabled, and a supported work/school account is used, the dialog should show the Proceed/Continue button so the GitHub integration can be completed.

References:

• Use GitHub with Loop
• Configuring external data integrations for Loop experiences