'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Currency Data Type Refresh Error in Excel & Microsoft 365
Question details
Users need to resolve a recurring refresh or account connection error when utilizing the Currency data type in Microsoft Excel.
- Product
- Microsoft Excel / Microsoft 365
- Device & OS
- not provided
- Scenario
- Refreshing live Currency data types in an enterprise environment, specifically when using Okta authentication for Microsoft 365.
- Observed behavior
- The Currency data type repeatedly displays a refresh error or prompts for an account connection, frequently occurring every morning after Okta sign-in.
Take note of the exact time the refresh error occurs and verify if any of your coworkers are experiencing the same issue, as this information will be necessary for IT support.
Check and Sign Out of Conflicting Office Accounts
Resolve authentication conflicts by ensuring only your primary Okta-linked account is signed in to Microsoft 365.
Having multiple accounts signed into Office can confuse the authentication process, especially when enterprise single sign-on (SSO) tools like Okta are involved. Clearing out secondary accounts often restores the data connection.
Launch Microsoft Excel and click on your profile picture or name located in the top right corner of the application window.
Review the list of connected accounts. Click 'Sign out' on any personal or secondary accounts that are not required for your current session.
Close Excel completely, reopen it, and sign back in using only your primary Okta-authenticated company credentials.
Select the cells containing the Currency data type and click 'Refresh All' on the Data tab to confirm the connection error is resolved.
Submit a Service Request via Microsoft 365 Admin Center
If the issue persists due to Okta integration bugs, your IT administrator must escalate the issue directly to Microsoft Support.
Switch to WPS Office for a Bug-Free Spreadsheet Experience
Tired of dealing with complex authentication loops and data refresh errors in Microsoft 365? WPS Office provides a lightweight, reliable alternative that lets you manage your financial spreadsheets locally without being blocked by enterprise cloud login bugs.
- 1. Download the Software: Visit the official WPS Office website and download the free version for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the quick on-screen instructions to set up the software.
- 3. Open Your Workbooks: Launch WPS Spreadsheets and open your existing .xlsx files directly. You can now work on your data without encountering Okta connection errors.
Frequently Asked Questions
Why does the Excel currency data type refresh error happen specifically in the morning?
In enterprise environments using SSO platforms like Okta, authentication tokens usually expire overnight. When you open Excel the next morning, the application struggles to refresh the live Currency data until the security token is properly renewed.
Can having multiple Microsoft accounts logged in cause data refresh issues in Excel?
Yes. Being signed in with multiple accounts (such as a personal account and a work account) can confuse Microsoft 365's authentication routing. This leads to connection errors when the software tries to fetch live data. Signing out of all secondary accounts usually resolves this conflict.
How do I report a persistent Okta authentication bug to Microsoft?
Standard end-users cannot report backend integration bugs directly. You must ask your organization's IT department or Microsoft 365 administrator to open a New Service Request through the Microsoft 365 admin center, detailing the Okta setup and affected user accounts.
