A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data
Hi @Matt Karee,
Based on your description, the newly downloaded workbook may still be receiving a Mark of the Web (MOTW) tag. If so, Excel will continue to treat it as an Internet-originated file and block its VBA macros, even though the main website has been added to Trusted Sites. This can happen when the file is delivered through a different hostname, subdomain, CDN, storage endpoint, or redirected URL.
A dedicated Excel Trusted Location can provide a supported operational approach. Files opened from a Trusted Location bypass several Office security checks, and active content, including VBA macros, can run. Because this location is highly trusted, only authorized users or applications should be permitted to add or modify files in it.
The person taking over the process could download the workbook and then save or move it into a designated trusted folder before opening it. However, I strongly recommend against marking the entire Downloads folder as a Trusted Location, because Office files downloaded from any Internet source into that folder could bypass the usual protections.
You can refer to: Trusted Locations for Office files
If your organization controls the workbook and its VBA code, digitally signing the VBA project and centrally managing the publisher certificate is generally a more secure and scalable approach:
- Sign the VBA project with an appropriate code-signing certificate.
- Deploy the corresponding public certificate to the Trusted Publishers certificate store on the devices that need to use the workbook.
- Configure the applicable Office macro policies according to your organization’s security requirements, such as allowing only macros that are validly signed by approved publishers.
Microsoft recommends digitally signing VBA code as a best practice for organizations that develop and distribute their own macros. Trusted Publisher certificates can be deployed centrally through Group Policy. If the signed VBA project is modified after signing, the signature becomes invalid, helping users and administrators identify that the code has changed.
Please note that other centrally enforced Office security policies can still affect whether a signed macro is allowed to run. Your IT administrator should review the effective macro policies on the affected device if the issue continues.
You can also refer to: Trusted publishers for Office files
These are simply my suggestions based on my experience and research, and I sincerely hope they provide some useful direction for your particular scenario.
Thank you for taking the time to review them.
If the answer is helpful, please kindly click "Yes" button below. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.