Trouble in running OfficeScripts in Excel Online Sharepoint

1)What does your Office Script do? 

It is just a simple worksheet to copy values from Sheet1 to Sheet2.

function main(workbook: ExcelScript.Workbook) {
  try {
    const sourceSheet = workbook.getWorksheet("Sheet1");
    const targetSheet = workbook.getWorksheet("Sheet2");

    console.log("Getting values from Sheet1...");
    const valueA = sourceSheet.getRange("A3").getValue();
    const valueB = sourceSheet.getRange("B3").getValue();
    const valueC = sourceSheet.getRange("C3").getValue();

    console.log("Setting values in Sheet2...");
    targetSheet.getRange("A1").setValue(valueA);
    targetSheet.getRange("B2").setValue(valueB);
    targetSheet.getRange("B3").setValue(valueC);

    console.log("Script completed successfully.");
  } catch (error) {
    console.log("Script error: " + error.message);
  }
}

2)Where is the Excel file stored? 

Sharepoint

3)How are you running the script? 

Manually in Excel Online; would want to schedule this in power automate later.

4. Have you checked for any error details in browser Developer Tools? 

Im getting these when i do F12:

Violation] Potential permissions policy violation: autoplay is not allowed in this document.Understand this error

6[Violation] Potential permissions policy violation: camera is not allowed in this document.Understand this error

6[Violation] Potential permissions policy violation: microphone is not allowed in this document.Understand this error

6[Violation] Potential permissions policy violation: clipboard-read is not allowed in this document.Understand this error

6[Violation] Potential permissions policy violation: clipboard-write is not allowed in this document.Understand this error

6[Violation] Potential permissions policy violation: display-capture is not allowed in this document.Understand this error

6[Violation] Potential permissions policy violation: keyboard-map is not allowed in this document.

js-wrapper.js:2 Blocked script execution in 'about:blank' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.

Refused to connect to 'blob:<URL>' because it violates the following Content Security Policy directive: "connect-src ". Note that '' matches only URLs with network schemes ('http', 'https', 'ws', 'wss'), or URLs whose scheme matches self's scheme. The scheme 'blob:' must be added explicitly.

The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate as value and it is preloaded intentionally.

Uncaught NetworkError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at ...' failed to load.

1. What does your Office Script do? 

Simple copy from one sheet to another

function main(workbook: ExcelScript.Workbook) {
  try {
    const sourceSheet = workbook.getWorksheet("Sheet1");
    const targetSheet = workbook.getWorksheet("Sheet2");

    console.log("Getting values from Sheet1...");
    const valueA = sourceSheet.getRange("A3").getValue();
    const valueB = sourceSheet.getRange("B3").getValue();
    const valueC = sourceSheet.getRange("C3").getValue();

    console.log("Setting values in Sheet2...");
    targetSheet.getRange("A1").setValue(valueA);
    targetSheet.getRange("B2").setValue(valueB);
    targetSheet.getRange("B3").setValue(valueC);

    console.log("Script completed successfully.");
  } catch (error) {
    console.log("Script error: " + error.message);
  }


}

1. Where is the Excel file stored?  Sharepoint
2. How are you running the script?  Manually; But want to schedule in Power Automate later
3. Have you checked for any error details in browser Developer Tools?  Getting these errors: js-wrapper.js:2 Blocked script execution in 'about:blank' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.

Refused to connect to 'blob:<URL>' because it violates the following Content Security Policy directive: "connect-src ". Note that '' matches only URLs with network schemes ('http', 'https', 'ws', 'wss'), or URLs whose scheme matches self's scheme. The scheme 'blob:' must be added explicitly.

1.

• Test with a simple workbook  Create a new .xlsx file with minimal content and try running a basic script to rule out workbook-specific issues. 

-- The issue persists

• Check file permissions  Make sure you have edit access to the workbook and it's not locked by another user. 

-- I have edit access

• Try running a sample script from Microsoft Learn  This helps confirm whether the issue is with your script or the environment: Office Scripts samples - Office Scripts | Microsoft Learn  --Same issue
• Run the script via Power Automate  If it works there, the issue may be specific to the Excel Online task pane.  -- It fails through Power Automate

Hi @Anu Tomy
Thank you for the detailed follow-up. 

Based on everything you've shared including the script, storage location, browser tests, and Developer Tools output it looks like you're encountering a platform-level issue, likely related to security policies or service behavior in Excel Online and Power Automate. 

Let’s walk through a few focused steps to help narrow this down: 

  1: Check Microsoft 365 Service Health 

Go to the Microsoft 365 Admin Center > Health > Service Health > Incidents, and look for any recent issues related to: 

• Excel Online 
• Office Scripts 
• Power Automate 

There have been past incidents (e.g., February and July 2025) where Office Scripts failed to run due to backend service errors. If you find a matching incident, note the incident ID and timestamp. 

2: Rule Out Browser Extensions, Proxy, or CSP Restrictions 

Try the following quick tests: 

• Open Excel Online in a private/incognito window with all extensions disabled. 
• Use a different machine and connect via a mobile hotspot to bypass corporate proxies or secure web gateways. 
• While reproducing the issue, keep DevTools Console and Network tabs open. Look for messages like: 
  • "connect-src blocking blob:" 
    • "sandbox … allow-scripts not set" 

These are strong indicators that a security control (CSP or proxy) is interfering with script execution. 

3: Test with a File Stored in OneDrive 

Create a new .xlsx file in OneDrive for Business and run a basic Office Script from Microsoft Learn. 

If the script works in OneDrive but not in SharePoint, this suggests that your SharePoint site may have custom policies or restrictions (e.g., CSP headers or sandboxing rules) that block script execution. 

4: Confirm Tenant-Level Settings 

Even though you've enabled Office Scripts, please double-check: 

• That the setting is enabled in both Microsoft 365 Admin Center and SharePoint Admin Center. 
• That no security baseline policies are blocking features like Web Workers or blob: URLs, which are required for Office Scripts to run in Excel Online. 

5: Capture Power Automate Error Details 

In Power Automate: 

• Open the Run History of the failed flow. 
• Click into the Run script action. 
• Copy the full error message, including: 
  • clientRequestId 
    • request-id 
      • UTC timestamp 

Since you've already tested across environments and confirmed that the issue persists even with basic scripts and clean workbooks, I recommend raising a support ticket with Microsoft. Please include:

• A description of the issue
• The script you're using
• DevTools Console output
• Power Automate error details
• Any relevant incident IDs from Service Health

You can raise a ticket via your Microsoft 365 Admin Center > Support > New service request.

Warm regards,

Hi @Anu Tomy
Just checking in, how’s everything going with the Office Scripts issue? Is it still happening, or have you noticed any improvement?

Have you had a chance to try the steps we discussed earlier (like testing in a private browser, trying a different network, or creating a new workbook on OneDrive)? If so, did anything change?

If the problem persists, would you like me to help you raise a support ticket with Microsoft? This can speed things up because the engineering team can review your logs and clear any service-side issues that might be causing the error.

And if my earlier answer was helpful, please consider clicking “Accept Answer” it helps others with the same problem find the solution faster.

Looking forward to your update!