<img alt="" src="https://secure.hims1nice.com/151009.png" style="display:none;">
" style="background-color: #2c3e50;">
 

Blogs

Building Business Resiliency Through COVID and Beyond

 

In a previous piece, we focused on how to rapidly implement Microsoft Teams in order to get your employees safely working from home. This is an excellent start, but you're not out of the woods yet.

Two self-inflicted “time bombs” that enabling your users to Work From Home (WFH) may cause.

 

Many organizations were forced to transition to a Work From Home (WFH) posture practically overnight and grapple with the numerous considerations the change brings with it. As the dust has (hopefully) started to settle and secondary and even tertiary items are being addressed, you may not be aware that there is a potential timebomb ticking away on your users' devices. This timebomb can strike when users begin returning to the workplace and have the potential to overwhelm the service desk with what is normally a minor and rare annoyance of an issue.

From Office 365 to Microsoft 365 – What’s Going to Change?

Microsoft 365

If there’s one thing Microsoft is unafraid of, it’s rebranding. We saw this play out as Lync became Skype for Business (which gave way to Microsoft Teams), and now Office 365 is becoming Microsoft 365. Right now, the M365 rebrand and updates are primarily consumer-focused, but some updates to familiar office suite applications are available to corporate users as well. What kind of changes – if any – can enterprise customers expect?

Need a rapid deployment of Teams? It is possible.

During our three-part series (starting here) on migrating to Microsoft Teams from Skype for Business, we gave you a lot of information on implementing a very slow and gradual transition. Unfortunately, things have changed. Due to the worldwide spread of coronavirus, you and all your co-workers are likely working from home, which means that your plans might need to accelerate dramatically.

KiZAN: Message from the President

During this time of uncertainty in our nation, I wanted to express a heartfelt appreciation to our employees, clients, and communities. We have all bonded together as a team and are accomplishing great things amid the disruption to our families, offices, and schedules. I truly believe that by continuing our united efforts, we will emerge stronger and better connected than we have ever been.

Best Practices for Migrating from Skype for Business to Teams Blog: Part 3 of 3

In this blog series, we have introduced various approaches for migrating to Teams (previous blog entries here: part 1, part 2). Whichever method you choose, you’re going to need to plan carefully.

First, understand who will be most affected by the changeover and get their opinions on the kind of support they’ll need. Then, create a transition timeline that ends with you switching over to Teams by or before the cutoff date. Only then can you choose the correct approach for your organization.

Best Practices for Migrating from Skype for Business to Teams Blog: Part 2 of 3

There is some good news. With a 2021 end of life deadline, there’s still plenty of time for you to train your workers and modify your applications. In addition, there are ways in which you can begin gradually introducing Teams, feature-by-feature, without immediately desisting from its predecessor.

(part 1 of our 3 part blog series is available here)

Best Practices for Migrating from Skype for Business to Teams Blog: Part 1 of  3

When Skype for Business replaced Microsoft Lync back in 2015, we thought that it would be around forever. Nothing remains static in the world of software, however. When Microsoft announced Teams just two years later, we all knew that Skype for Business would one day come to an end. Skype for Business Online will be formally retired on July 31, 2020, and thereafter all-new Office 365 users will be onboarded directly to Teams.

What Is Automation and How BPA Helps Your Business

 

The inefficient, manual, repetitive task is ingrained into the day-to-day operations of most businesses.  It manifests itself in a variety of ways. 

Common Scenarios: 

  • The cutting and pasting of data from one report into a spreadsheet in order to produce "the real" report

  • The upkeep and use of an obsolete system or software “because it contains valuable information”

  • The laborious reconciliation of timesheets, billings, expenses or “non-accounting” data

  • Unsecured paper/document-based messaging or communication workflows

Website