AccountRight and MYOB Business outage
Resolved - MYOB Business and AccountRight outage Update - 03/09/2023 - 11.30 AM AEST We are pleased to advise that the service has now been restored following the recent Microsoft Azure outage. Essentials, AccountRight Live and MYOB Business are operating as normal. MYOB and Microsoft will continue to closely monitor our systems in the coming days. We apologize for the inconvenience caused as a result of this outage and thank you for your patience as we’ve worked to resolve this issue. Our cloud service provider is currently experiencing a major outage affecting the Australia East region. This is impacting our customers and the ability to access their company files on AccountRight and MYOB Business. To stay up to date please visit https://status.myob.com Update - 31/08/2023 07:18:55AM AEST We are still seeing intermittent errors or instability in services, some customers will be experiencing errors loading or slow performance accessing our online products. We continue to work with our cloud service provider to stabilise the system. Update - 31/08/2023 03:10:32PM AEST We are continuing to work with our cloud service provider to identify alternate solutions to restore service to those still impacted, alongside their primary restoration activities. They have not been able to provide an estimated time to restore service. Delivery of bank feeds data is ongoing. Thanks for your patience while we work on it. Update - 31/08/2023 10.18AM AEST Hi everyone, we're pleased to report services are coming back online and returning to normal levels of performance. While services resume, some of our customers will experience some slowdown or login problems, but we are on track to be back to full speed soon. Keep track of our progress at status.myob.com. 31/08/2023 12:54:56PM AEST We are continuing to work with our cloud service provider to restore service for those that are still experiencing errors affecting access and performance of our online products. We understand that the provider is still working to recover some of the infrastructure that hosts our services, they remain unable to provide an estimated time to restore service. Update - 31/08/2023 07.15 PM AEST An evening update for you all. For the vast majority, services should now be up and running as normal. But for a select few, we understand there are ongoing performance and access issues which we are investigating as a matter of priority. We are sorry to those still impacted and are committed to keeping you updated on our progress as we work this through with our cloud provider. Update - 01/09/2023 07.14 AM AEST Overnight we have worked directly with our providers engineering team, who have been migrating our residual affected services across to working infrastructure. Some progress has been made to restore a number of affected services, but the work continues and they acknowledge that although the majority of their customers are now functional "A subset of services still experiencing residual impact are on the path to mitigation". We will continue to keep you updated as work progresses. Update - 01/09/2023 10:15AM AEST We are reading your messages and are aware that there are a number of customers still affected by our cloud providers' outage on Wednesday evening. We are continuing to work closely with our cloud provider as a top priority to diagnose the impacts and return services to normal levels for all those impacted. While for the majority of our customers the matter is now resolved, we appreciate that a proportion are still experiencing some delays in service and login difficulties. We understand this has happened on a critical last-of-the-month day for you, and that business processes have been disrupted as a result of the outage. Resolving these issues is our greatest priority and we are committed to keeping you updated on our progress. We will be providing updates via this channel every hour, and you can also find more information at https://status.myob.com. Update - 01/09/2023 02:25 AEST We are working with our cloud service provider to restore access and performance to the remaining affected services. They are continuing to migrate our residual impacted services to working infrastructure. We will keep you updated as we make progress. Some of you may also note a delay in delivery of some Bank Feeds data, this is related to this incident. We are seeing a backlog of data processing, however delivery will be later than usual. Update – 01/09/2023 05:18PM AEST Hi Everyone, On 30 August 2023, MYOB’s cloud service provider, Microsoft Azure, experienced an issue which has caused disruption for customers accessing their MYOB solution. This issue also impacted several other major Australian organisations. While the issue is now resolved for most MYOB customers, we’re aware some of you are still experiencing login difficulties and service delays. We understand this has happened at a critical time at the end of the month, and that business processes have been disrupted due to the outage. We are focused on resolving this issue and apologise for the disruption and difficulty this has caused. We continue to work closely with Microsoft to return services to normal levels for all those affected. To keep updated on our progress, please visit our Status hub Update - 02/09/2023 - 09.30 AM AEST Hello everyone, We wanted to keep you updated on our efforts to restore service for some MYOB customers following the recent Microsoft Azure outage. While most services have been resumed, some customers may still be experiencing ongoing or intermittent problems with their MYOB solutions. We continue to work closely with Microsoft to return services to normal levels for all those affected. We are focused on resolving this issue and apologise for the disruption and difficulty this has caused. To keep updated on our progress, visit StatusHub. Update - 02/09/2023 - 01:15 PM AEST Efforts to restore service for some MYOB customers impacted by the recent Microsoft Azure outage are progressing. While most services have been resumed, we continue to work closely with Microsoft to return services to normal levels for all those affected. Some customers may still be experiencing ongoing or intermittent problems with their MYOB solutions. We apologise for the difficulty and inconvenience this has caused and we are committed to resolving all remaining issues as soon as possible. We will continue to keep our customers updated via the Community Forum and further updates are available at StatusHub. Thanks for your patience.52KViews35likes509CommentsEnhanced security measures are live - 27/11/24 (Update 19/12/24)
Hi everyone, Update 19/12/24 - Are you still there? Hello Community members and followers of this security updates thread! Its been a few days since we last spoke. There is a great update coming through already for the inactivity timeout changes in the browser. AND its releasing Today the 19/12/24. Users in the browser will now be provided with a warning message 5 minutes prior to the inactivity timeout. This will show at the top of the window with "Are you still there?" and provides a clickable option to confirm "I'm still here" - example image below Update 05/12/24: Session Inactivity Lock for AccountRight Desktop App We've consulted with the ATO and have been able to agree that AccountRight Desktop can be excluded from the 30 minute inactivity lock requirement. We can confirm this feature has now been removed from the desktop app. While the inactivity lock is no longer in place on the AccountRight desktop app, we strongly encourage everyone to implement sensible security measures on your individual devices. This includes setting up automatic timeouts and using password-protected logins for added protection. The 30-minute inactivity lock will remain in place for MYOB Business and MYOB AccountRight in the browser, in line with ATO requirements. Previous update to this post (27/11/24) The changes for inactivity went live today on the 27th November. Specifically for AccountRight, many customers encountered unexpected crashing/freezing of the software after entering their password to sign in again. Work in progress would also be lost due to the crash. I want to assure everyone that this is not the expected behaviour associated with the inactivity timeout. You can expect the screen to blur and a message pop up. Click sign in again as [user]. Enter your password and you will be back to continue where you were (no loss to work in progress) As a result of the crashing, we have temporarily disabled the inactivity timeout for AccountRight, you will need to close and re-open AccountRight for this change to take effect. Thank you for the feedback, examples and information provided on these issues today. We are continuing to investigate before it is enabled again. I’m updating this post (2:30pm AU 21/11/24), as there have been a lot of comments and engagement in the change. With over 100 comments on the post, we are starting to get the same questions being asked, and answers being missed so I hope to summarise the change and key questions/feedback here. The change/s and timeline September 30 th > MYOB implemented 2FA being required at least once every 24 hours Some initial feedback came through about the 2FA prompt caused customers to lose work in progress MYOB has implemented a fix based on feedback and 2FA is prompted on the first login each day to avoid loss of work November 27 th > you'll be asked to sign back in after 20-30 minutes of inactivity (announced November 19 th ) This announcement on inactivity is driving a significant amount of feedback and discussion that I will summarise below What’s changing: From Wednesday 27 November 2024, you’ll be asked to sign back in after 20–30 minutes of inactivity. After this time, your screen will become locked and blurred. To continue working, you'll need to sign back in with your username and password. This applies to the following MYOB software: MYOB Business, MYOB AccountRight and AccountRight browser (online files only), MYOB Connected Ledger, MYOB Business Payroll Only and MYOB Practice. Browser: Desktop: What do you need to do? When you’re presented with the Are you still there? message we recommend that you click Sign in using [existing email] to return to work in progress. Note* 2FA is not required as part of signing in again and your email will automatically be pre-filled Will I lose my work when the screen is greyed out? If you sign back into your account using your existing email, you won’t lose any work in progress and can continue where you left off. However, if you choose to sign in to a different account, your work will not be saved. If you click Back or Reload, or if you don’t sign back in after 12 hours, you'll also lose work in progress. How does the inactivity screen work between Browser and Desktop? When you are logged into both the Browser and Desktop at the same time, each session will operate independently. This means that if you are inactive in the Desktop version, you can remain active in the Browser version. The inactivity timeouts for these sessions are separate from one another. When signing back in after inactivity, do I have to enter my email, password and do 2FA? No, your email will be automatically pre-filled when signing back in using your existing email to both the desktop and browser software. Users will be required to enter their password only. 2FA is still a 24-hour requirement and not required for signing back in after an inactivity timeout. Can I opt out of the new inactivity or 24-hour 2FA security measures? No, as these are mandatory compliance changes in line with industry best practice, they cannot be disabled Why am I being asked to login or do 2FA multiple times a day? Based on scenarios described in the forum + a known issue that MYOB is currently working to resolve, this could be for one of the following reasons. Closing AccountRight using the ‘x’ is currently causing 2FA to be prompted when re-opening the software even if it is less than 24 hours. This was recently discovered as a bug/regression with the last AccountRight 2024.10 release and the team are releasing a fix to this asap. This has been resolved* Opening multiple instances of AccountRight. This seems to something multiple customers are doing when they have multiple files they work on. Instead of switching between files (no login would be required) they are all opened concurrently and each instance of AccountRight that is opened will require a login Is this an MYOB decision or required by the ATO? And subsequently, why do New Zealand customers need to adhere to ATO requirements? Yes, both the 24 hour 2FA and the inactivity timeout changes are mandated requirements from the ATO. This requirement seeks to minimise the opportunity for unauthorised users to access Taxation, Accounting, Payroll, Business Registry or Superannuation related information. Read more on the ATO website here if interested New Zealand customers, although not bound by the same requirements set by the ATO, will share the same security measures as our Australian customers so that MYOB is providing best practice security to all customers. MYOB has also published help articles that explain the changes and can be found below For Australian customers here For New Zealand customers here6.3KViews6likes273Comments