Modern Authentication in SPOC Cloud Update FAQ
Please see below for common questions regarding the update of the the Gimmal Records Cloud SharePoint Online Connector.
Last updated:
Some of the linked articles refer to the on-premises version of the tool. The details are identical for the Cloud version. Documentation for the Cloud version will be updated well before deployment.
Q: When will SPOC be updated to use Modern Authentication?
A: The SPOC updates will be rolled out to different tenants over the month of February 2026:
· February 5th and 6th : All SPOC Test Sites updated (Downtime Required)
· February 13th : Canada and UK SPOC Production sites updated (Downtime Required)
· February 20th : United States SPOC Production sites updated (Downtime Required)
Q: How long is the maintenance window?
A: The duration of the maintenance window will be communicated to you in reminder emails. You can expect the maintenance window to last from 6pm US Eastern Time on Friday through 6pm Eastern Time on Sunday. Actual downtime may be shorter.
However, all processing performed by the SPOC connector will be halted until the relevant credentials and configuration are successfully entered into the SPOC application configuration by the administrator account. Gimmal will inform the admin accountholders and key customer contacts as soon as their tenant update has been completed. See SPOC Configuration starting at Step 2 for details.
Q: What information will Gimmal need from me to successfully update SPOC to Modern Authentication?
A: Well before your tenant is updated, Gimmal will need you to provide at least one administrator account which will be used to manage the SharePoint Online Connector and configuration. This serves as the initial connector administrator and the credentials should be kept in a secure place.
If you have not already received communication requesting this information, please contact Gimmal support at help@morae.com
Q: What kind of account is needed for the SPOC Administrator Account ?
A: The following must apply to this account:
It must be a valid Entra ID (formerly Active Directory) login
The username suffix must match the registered Gimmal Records tenant domain (e.g. user@foolalatenant.com for FooLaLaTenant).
The account must be able to receive email. Gimmal Records needs to be able to send an email inviting the account to join the B2B collaboration. (Note: This collaboration may already be established with an existing account and therefore may not be sent.)
Q: What do I need to do before deployment?
A: You will need to create an app registration. Please see Preparing for Modern Authentication for detailed steps.
Q: Can I use a wildcard certificate as part of registration?
A: Yes. however, for production environments, we strongly recommend that you acquire a certificate from a reputable public Certificate Authority.
Q: What do I need to do after deployment?
A: You will need to configure SPOC to ensure communication to your M365 tenant. You will need the Client ID and Tenant ID created before deployment. See SPOC Configuration starting at Step 2 for details.
Q: What is the SPO Redirect URL referenced in the SPOC Configuration document?
A: The SPOC Configuration guide mentions that you will need to enter a redirect URL as part of app registration. The redirect URL to use is dependent on your region (US, UK or Canada) and type of deployment (Test/Prod). See chart below. If you are unsure of your region, please contact Gimmal Support.
Region | Test Redirect URL | Production Redirect URL |
|---|---|---|
United States | https://spo-records.gimmal.build | https://spo-records.gimmal.cloud |
Canada | n/a | https://spo-records-ca.gimmal.cloud |
United Kingdom | https://spo-records.uk.gimmal.build | https://spo-records.uk.gimmal.cloud |
Q: After the update, will SPOC automatically restart processing?
A: No, you must first enter the configuration. Once you have confirmed successful connectivity, the connector will process all records accumulated during the downtime period. See SPOC Configuration starting at Step 2 for details.
Q: Will I expect disruption to my service?
A: Yes. The connector service will stop processing from the period of the update and up until the credentials have been entered and validated. At that point, processing will continue where it left off with no other outside intervention needed and no data lost.
See SPOC Configuration starting at Step 2 for details in for updating the configuration.
Q: Do I need to to reconfigure any sites post-deployment?
A: No, all registered sites will automatically use the new SPOC connector.
However, if you use the ‘Manage Record’ button feature:
There may be some artifacts of the old system remaining which you may want to clean up manually remove the existing connector app from
Currently managed sites
The App Catalog
You will need to install the the new connector app in the app catalog and associate it to the currently managed sites. Please see this article for step by step details.
Q: How to I manage SPOC going forward?
A: Please see the following articles for details. Although they refer to the on-premises version, the management details are nearly identical for the SPOC Cloud version.
User Management Note: Service accounts will already be established are part of the pre-upgrade preparation.
SPOC Configuration starting at Step 2
Q: Will any functionality change with this update?
A: Yes. Three key areas have been updated:
Authentication
The SPOC configuration now includes parameters to support Modern Authentication
Client/Secret is no longer supported
The method for registering SharePoint Sites has changed.
If used, the 'Manage Record' button in SharePoint will now point to an updated ‘Record Overview’ page.
Q: Will I need to provide a Client ID and Secret to Gimmal after the update?
A: No. Client ID and Secret are no longer used for authentication and are not needed. All authentication will be configured via the app registration in Microsoft Entra which is controlled by your organization. Please see Preparing for Modern Authentication for detailed steps.
After deployment, a SPOC administrator will need to enter the appropriate Client ID and Tenant ID into the SPOC connector configuration. This allows the connector to successfully communicate with your M365 SharePoint instance. See SPOC Configuration starting at Step 2 for step by step details.
Q: Will the older Add-In Model still work for SPOC after the cloud has been updated?
A: No
Q: Who do I contact with any Issues or Questions?
A: The Gimmal team will be in contact throughout this process. For anything further, please contact your account representative or Gimmal Support.