Featured

The Latest

22 October 2021: Google’s latest digital solutions, product features and partnerships were unveiled at Google Cloud Next ’21. In this three-day event, Google and Alphabet chief Sundar Pichai and Google Cloud CEO Thomas Kurian led the keynote sessions on Google Cloud’s improved customer ecosystem and security capabilities.

Possibly the most significant announcement at the event was around Google Distributed Cloud. The Google Distributed Cloud (GDC) platform allows deployment of Cloud-native architecture to private data centres. GDC Edge provides capabilities to run applications at the ‘far edge’ of organisations - IoT devices, AI enabled devices, and so on - via low-latency LTE, radio access network (RAN) networks, and newer 5G Core network technology.

Google Distributed Cloud does not require enterprises to connect to Google Cloud when using their APIs or managing network infrastructure. This is important for organisations (e.g. public sector, finance, health) needing to retain on-premises deployment for tighter control over security and compliance.

Why it’s Important

With GDC, all the top three hyperscale Cloud vendors now have options to run applications developed for public Cloud across private and semi-private infrastructure. Furthermore, all three vendors have approaches to ‘edge’ computing. This is a natural evolution of the operational practices, automation and management software, software defined networking and hyper-converged infrastructure (HCI) that sees the Cloud seeping back into all areas of ICT. As this trend continues, and the lines between where ‘Cloud infrastructure’ sits, organisations will need to make decisions on the key automation and management platforms they will adopt across Clouds.

More organisations have started looking for better solutions to place their Cloud resources anywhere and in any geolocation. This offers considerable reductions in latency by eliminating the distance between users and their content to ensure highly available data while keeping costs low.

Who’s impacted

  • CIO
  • Development team leads
  • Business analysts

What’s Next?

All the hyperscale Cloud vendors are offering this type of flexibility and they are strongly expected to improve over time. It will further drive hyper converged infrastructure (HCI) investments driven by the demand for cost-effective scalable storage with strong durability and availability guarantee.

Related IBRS Advisory

The Latest

22 October 2021: At Google Cloud Next ’21, Google announced the general availability of a PostgreSQL interface to its hyperscale, global spanning Spanner relational database. In short, this means that organisations that have applications that are compatible with PostgreSQL can now migrate to a highly elastic database that is significantly less costly, more robust than running PostgreSQL instances on virtual machines.

Why it’s Important

Google’s highly scalable Cloud relational Spanner database provides high-velocity transactions, strong consistency, and horizontal partitioning across global deployments. Like other specialised, serverless Cloud databases, Spanner previously required legacy (on-premises) applications’ data access layers to be reworked. 

The addition of a PostgreSQL interface greatly reduces development teams’ workload for migrating applications to Spanner. This has several knock-on impacts when migrating applications to the Cloud, including: 

  • reducing training  / new skills development, and allowing existing skills to be fully leveraged
  • reducing the vector for new bugs to be introduced
  • simplifies testing

Overall, this significantly lowers the cost and risk of moving an app to the Cloud. 

As always, the devil is in the detail. Cloud Spanner Product Manager, Justin Makeig posted that the platform does not yet have universal compatibility for all PostgreSQL features, since the company’s goal was to focus on portability and familiarity. However, IBRS has determined that even with the current level of functionality, the PostgreSQL interface for Spanner presents good value for teams looking to migrate legacy applications to the Cloud.

Google is not the only hyperscale Cloud vendor that has enabled this type of operability. However, Cloud Spanner is more economical than competitive hyperscale Cloud database products at this time.

Who’s impacted

  • Development team leads
  • Cloud architecture teams

What’s Next?

Google announced that it is planning to expand its Spanner integration to additional database standards. Data portability and migration of legacy applications to hyperscale Cloud is now a focus for many ICT groups. The availability of open standard SQL interfaces to database PaaS (platform-as-a-Service)  is expected to be a trend for application and data migration, especially where the applications are complex.

Related IBRS Advisory

  1. VENDORiQ: Google introduces Database Migration Service
  2. Enterprise resource planning (ERP) Part 5: Will automation of S/4HANA data migration make modernisation

The Latest

22 October 2021: Google introduced the Work Safer program at the Google Cloud Next ’21 event. The new program includes the Google Workspace suite of products, and adds several third party cyber security services for endpoint security and access to legacy solutions. In addition, Google unveiled upgraded devices, including new Chromebooks from HP.   

A new in-house Google Cyber security Action Team was also introduced in the event. The group will take the lead in developing cyber security and digital products by leveraging the capabilities of the Work Safer program and developing training and policy materials..

Interestingly, Google is offering a whopping 50% discount for the term of the initial contact for all products (its own and third parties) within the Work Safer program.

Why it’s Important

The aim of the Work Safer program is to reinvigorate interest in the Google Workspace ecosystem.  

Microsoft continues to have a near monopoly on the office productivity space, and is using that position to drive organisations towards its Azure Cloud ecosystem and its security ecosystem. Microsoft’s strength is its breadth of services, support for legacy solutions and resistance to change by both desktop teams and office staff.  Creating sufficient impetus for change to a light-touch, collaborative environment of the magnitude Google proposes is hard.

Google Workspaces has a far smaller attack vector compared to Microsoft. Its architecture has been firmly rooted in zero trust since its inception - from the devices all the way to the apps, storage and access controls. However, organisations that have not yet gone down the Google path retain a significant array of existing network investments, legacy solutions, mixed access controls and identity management, devices and so on. To meet these clients' needs, Google has partnered with CrowdStrike and Palo Alto Networks to come up with endpoint protection and threat detection solutions. The partnerships should not be viewed as “Google is backfilling weaknesses in its ecosystem” (which is something we expect to hear from Google’s competitors soon. Instead, these partnerships should be viewed as Google recognising its ecosystem will need to sit alongside ecosystems based on architectures that were conceived several decades ago and retain complexities that need to be addressed.

With more businesses shifting to a remote or hybrid work setup, the risks of ransomware attacks through phishing campaigns, malware infections and data leaks pose a threat to these companies’ data security practices. As such, Google easily benefits from its product’s value proposition already being consumed.   

Therefore, it would appear that Google’s messaging is on point. 

However, from roundtable discussions with digital workspace teams held this month, IBRS has confirmed that Australian organisations’ ICT groups and senior executives continue to resist a major step-change in the office productivity and device space. Rather, most organisations continue to look for ways to extract more value from their existing Microsoft contracts, increasingly looking to expand their investments into Microsoft’s E5 security offerings.  

In short, Google’s challenge is not convincing organisations they have a better, leaner security model. It is not even being less costly than Microsoft.  

It is literally resistance to change.

Who’s impacted

  • CIO
  • Development team leads
  • Business analysts

What’s Next?

Even if an organisation is unlikely to switch to Google Workspace, it is beneficial to review Google’s architecture and which aspects can be applied to the existing architecture.

Organisations should also consider running Google Workspaces experiments with groups of remote / hybrid workers that have less connection with legacy solutions.

Related IBRS Advisory

  1. Deciding between Google G Suite and Microsoft Office 365
  2. Considering Chromebooks Part 1: Show me the money!
  3. Chrome OS: Follow the money

The Latest

22 October 2021: Microsoft recently unveiled the latest versions of its Surface line of devices with versatile form factors to cater to different use cases. Highlights include the redesigned 13-inch Surface Pro 8 tablet with 11th generation Intel processor, the portable Surface Go 3, the laptop/tablet Surface Pro 7+, the pocket-sized Surface Duo 2, and the highly anticipated Surface Laptop Studio.

Why it’s Important

Microsoft released its redesigned Surface lineup form factor alongside its rollout of Windows 11 earlier this month. While there are plenty of improvements in the new lineup, most are best described as evolutionary: more computing power, refinement of form factors, etc. 

However, two products stand out as potential new niche market makers: the Duo 2 and the Surface Laptop Studio.

The Duo 2: Win-Win or Double-Trouble?

IBRS has obtained a Surface Duo 2 and finds it fits somewhere between a smartphone and a tablet… yet not quite matching either role. While Samsung found some success with its Galaxy Z Fold device as a smartphone, the Duo 2 tends more towards the tablet end of the market.

If the Duo 2 is to be successful, it will be due to Microsoft defining a new niche for mobile prosumer (professional- level consumers). The success of the device will indicate that there is no single market niche for foldable devices (as they are currently being touted), but several sub-niches tied more to screen size, onscreen keyboard capabilities and photography prowess.

On the flip side (pun intended), first impressions of the Duo 2 suggest it may be a workable alternative to the semi-ruggedised, larger format smartphones which are making inroads against traditional fully-ruggedised tablets. 

The additional screen space and size of the on-screen keyboard, positions the Due 2 slightly above most of the large format phones for field workers. It is even passable (just) for running remote virtual desktop applications. 

Surface Laptop Studio: Solves the problem you didn’t know you had

IBRS has also trialled the Surface Laptop Studio. IBRS believes this device serves a new niche between more traditional laptops (such as the Surface Book) and hybrid devices (such as the Surface Pro).  

The Laptop Studio has a hinge at the back to help set up the device in three versatile constructions: a regular laptop, a ‘stage’ mode where the screen is closed when streaming or engaged in video calls, and the ‘studio’ mode where the screen slides out flat, effectively turning the device into a graphic-intensive tablet.

From observations during ‘digital workspace’ consulting engagements, IBRS has noted that the Surface Pro is often used as a ‘primary desktop’ (meaning, used mostly when seated as a staff-members regular desk and in the home office). The weakness here is that the device is better suited for mobile (nomadic) work.

The Laptop Studio is more geared towards a desk-top experience, while also providing for flexible user configuration. For example, it features more connectivity ports, but less focus on the battery 

Microsoft is not the only company implementing a new form factor to cater to users’ needs for devices that straddle between existing designs. Acer’s ConceptD 3 Ezel and HP’s Spectre Folio also share the same form factor as the Surface Laptop Studio. 

It is likely this ‘desktop oriented yet flexible’ form factor will gain ground as more organisations adapt to the demands of hybrid working. It is not enough to consider someone working between multiple office locations as being a ‘remote worker’. Rather, they are full-time office workers that may wish to move between locations, while gaining the ability to host video conferencing, engage in pen / tablet creative work, and switch back to having a more traditional desktop experience.

Who’s impacted

  • Procurement
  • Digital workspaces / end-user computing teams

What’s Next?

The evolution of end user devices is ongoing - albeit slowly and with more than a few dead-ends. Manufacturers continue to experiment with new market niches, as organisations become more selective with devices that meet specific needs.  

The upshot of this is that care should be taken when developing ‘personas’ for digital workspaces. Keep in mind that a persona is not solely related to a staff member’s ‘job’ (which is really multiple different types of jobs). It needs to factor the environment, the tasks performed in the context of the environment, and the staff's ability to switch between different devices based on needs at any given time.

In addition, when determining mobile force field device needs, do not limit the evaluation to the features of fully rugged products. Instead, consider the lifecycle of the products and software dependencies. Only then should an organisation decide which available devices on the market can best cater to the work contexts and personas you have.

Related IBRS Advisory

  1. Redefining what ruggedised means
  2. The use and abuse of Personas for end-user computing strategies
  3. Examples of Persona Templates
  4. VENDORiQ: Samsung unveils new smartphones

When your business faces a disaster it is key to address the issue head on. You must first understand who's problem it is to solve and create an effective disaster recovery (DR) plan. Both business and ICT need to be comfortable that the DR plan has been verified to ensure a reasonable expectation that recovery will be successful. IBRS has created a 4 part series to help organisations plan for and recover from disasters successfully. Download the 'disaster recovery must work ebook' and prepare your organisation.

Conclusion:

In the modern business landscape, ICT products and services are becoming more and more critical to the success of the business. It is now more common than not that ICT products and services are being delivered through outsourcing of some kind, using Software-as-a Service (SaaS) or Cloud service providers (CSPs). Innovating improvements to the business can become a challenge when your organisation is tied to delivery of ICT services under contract; most very specific in nature but key to delivering success.

The key to successful innovation is situational awareness across both the business and the ICT environment. The result of being able to achieve situational awareness will enable both business units and ICT to innovate with their eyes wide open to both the opportunities and constraints impacting the business. The true cost and time to market the innovation presents, can then be clearly understood against the benefits envisaged.

Conclusion:

As organisations flesh out their detection and response strategies, one new area of applicability of this technology deserves serious consideration. The new area is identity detection and response (IDR). Most of the current detection capabilities are clustered around the malicious actor’s activity across the infrastructure. Activities such as lateral movement using networks, system compromise using fileless malware, and even social engineering users to act on the attacker’s behalf.

Yet identity is the holy grail sought out by malicious actors in almost every penetration of a system. It is central to every IT environment. Organisations should examine IDR and assess the visibility it may bring to their detection systems.

Conclusion:

Project prioritisation is a critical element of ensuring that limited resources are applied to the most appropriate initiatives, and result in the biggest bang for the buck. In a constrained financial environment this is even more critical, and will reveal inappropriate models, failures in governance, and decision making and the potential for missed opportunities or wasted resources. Identifying an accepted model is only one step and understanding the challenges in applying a prioritisation approach effectively will result in a far more productive outcome.

The Latest

27 August 2021: Security flaw hunters at Wiz were able to obtain the security keys that control access to Microsoft’s Azure Cosmos DB, and demonstrate that it was possible to access customers’ Azure Cosmos DB.  

Why it’s Important.

This flaw is especially worrying, because all Cloud vendors and many independent security advisors, including IBRS, have been advocating that Cloud security is generally of a far higher standard than that achieved by most in-house data centre teams. IBRS stands by this claim. But this does not mean Cloud vendors will not make security mistakes. And when they do, they will impact large numbers of organisations.

There is no evidence that this security flaw - likely an operational oversight - has been exploited. Once it was identified by Wiz (on the 9th August) and flagged with Microsoft (on the 12th August), the existing keys were quickly re-secured. Unfortunately, the keys in question are fundamental security assets that Microsoft cannot change. Therefore, Microsoft emailed the customers (on the 26th Aug) requesting they create new keys, just in case the previous keys had fallen into the hands of bad actors. It is estimated that 3300 customers have been impacted. 

To mitigate this issue, Microsoft advises Cosmos DB customers to regenerate their Cosmos DB primary keys immediately.

Unfortunately, just because there is no evidence the flaw had been leveraged, organisations should assume the worst. It is well publicised that state-actors hoard such flaws for intelligence gathering. In this case, paranoia may be justified.

More importantly, the situation highlights the need to take a multi-level approach to security in the Cloud. Relying on security protocols to secure an essential asset places organisations at greater risk of these hyper-scale security flaws.  

For example, in this situation, organisations that have behavioural/usage pattern analytics monitoring the database would likely have been altered should any bad actor start to access the database, and remedial action would be triggered. Furthermore, data from such monitoring could be used to determine the likelihood that the security flaw had been exploited - something few Azure Cosmos DB customers can confirm at the moment. 

Another example is using encryption services, these services should be leveraged extensively. Assume data assets will leak and repositories (including databases) will be breached, base encryption strategies on the sensitivity of the data. 

A migration to the Cloud can often improve the security stance of an organisation, but only if security is treated as a multifaceted, ‘trust nothing’ (akin to zero trust) philosophy is taken.

Who’s impacted

  • CISO and security teams
  • Cloud architects
  • Cloud migration teams

What’s Next?

  • If you are an Azure Cosmos DB client or have instances in development teams, immediately regenerate the primary keys for these databases.
  • Review your Cloud solution designs - including those of ‘lift and shift’ of legacy systems - to identify where single points of security failure could occur. Consider remediation strategies using multi-facilitated security services risks. Such effort needs to be balanced against business risk and information sensitivity. 

Related IBRS Advisory

  1. Cloud Security Considerations – Lessons from the Frontline
  2. CyberArk launches AI-powered service to remove excessive Cloud permissions
  3. New generation IT service management tools Part 2: Multi-Cloud management

The Latest

19 August 2021: Microsoft has announced pricing increases for its Office 365 and Microsoft 365 offerings, which has resulted in a great deal of media coverage.Microsoft is at pains to point out that it has not increased its prices on 365 for a decade, and during that time has added a great deal of functionality (20+ applications) to the portfolio.

The Specifics

Microsoft is still working through how the new pricing will be applied in the Australian market and an announcement is expected soon. IBRS will perform a detailed cost analysis at this time. However, Microsoft has confirmed that any changes to local pricing will mimic the North American price changes. 

Based on the US data, enterprise and business plans will see increases in March 2021. Based on US$, the dollar amounts range from US$1 to US$4 per user per month, or US$12 to US$48 per user per year, with the percentage increases running from a low of 9% to a high of 25%. Microsoft F-series licences for frontline workers and Microsoft 365 E5 are not subject to price increases. Consumer and education-specific plans (the A-series) are also unaffected by the price increases.

The new pricing structures will disproportionately impact small businesses and those with the lower levels of the Microsoft suite, while enterprises with E5 licences will be left unscathed. That in itself reveals Microsoft’s clear intent to nudge the market towards its E5 offerings. It is estimated that only 8% of Microsoft customers globally opt for E5 licensing, though IBRS has seen strong interest among Australian organisations to at least explore the more expansive capabilities found in E5.

At this time, we believe the majority of IBRS clients will see price increases in the lower range. However, given that Australia has been one of the fastest adopters of Office 365, and has for decades suffered from ‘the Australia tax’ of software vendors, the increases will still be felt deeply across the industry.

Why it’s Important.

For many IBRS clients, the immediate impact is the need to set aside extra budget for its existing 365 environment. 

Something that is not gaining attention is that the new pricing also increases the cost of Microsoft’s Unified support, since it is calculated as a percentage (10-12%) of the overall Microsoft spend. IBRS recommends that organisations set aside a budget for this increase as well.

However, the price increase is not the full story. A closer look at how the new pricing is structured, plus other less publicised changes, suggests it is geared towards making E5 licences more attractive to mid-sized organisations. 

The increases came shortly after Microsoft announced that its perpetual-licence Office would see a 10% increase and that its service for Office would drop from 7 years (it was previously 10) to just 5. Even more telling is that Microsoft has effectively engineered a one year ‘gap’ in N-2 support for Office (with the persistent licensing model), which forces organisations with older Office Pro licences to either purchase an upgrade sometime before 2023, or migrate to Office 365. 

In summary, Microsoft’s recent changes to Office licensing are a strategy that makes the price difference from E3 to E5 licensing less imposing and makes sweating perpetual Office licences far less attractive, if not unworkable. The savings from sweating Office licences over a five-year period are still there, but they are significantly lower than with seven-year cycles.

IBRS has long stated that Microsoft’s goal is not necessarily to drive up ICT budgets. A closer look at the additional capabilities found in E5 licensing reveals that most are aimed at moving Microsoft into adjacent product sets. For example, the additional security capabilities that become available with E5 licensing are clearly aimed at security incumbents, such as Symantec. Microsoft’s E5 strategy is to pull ICT budget away from competitors and into its own coffers. It is about carving out competition.

Who’s impacted

  • CIO
  • CFO & procurement
  • Digital workspace teams

What’s Next?

In the Australian market, IBRS sees few enterprises still on persistent licensing for Office. Globally, Australia has been an early adopter of E3 licensing, though until the mass push to work from home in 2020, many organisations did not take full advantage of the additional features and collaboration capabilities of the 365 platform. Furthermore, Google Workspaces is only making marginal increases in the local market, meaning Microsoft has little real local competitive forces working to temper it in the office productivity space (though this is not the case in other markets in the Asian region).

Therefore, the question for organisations is, is this strategy to push customers from existing E3 licences to E5 licences a trigger to start re-evaluate ways to leverage more value from the Microsoft ecosystem (that is, double-down on Microsoft).  

Organisations may respond to this price increase and Microsoft’s strategy to push customers from existing E3 licences to E5 licences as a trigger to:

  1. Re-evaluate ways to leverage more value from the Microsoft ecosystem (that is, double-down on Microsoft).  Just prior to this announcement, IBRS had drafted a paper on how to decide between E3 and E5 licensing. It is due for publishing in the coming month. However, if you wish an advance (draft) copy, please request it from nbowman@ibrs.com.au. It is focused on how to evaluate the additional benefits of E5 in the context of your existing software ecosystem.
  2. Set up a ‘plan b’ for enterprise collaboration. In a practical sense, this would likely be a shift to Google Workspace for part of the organisation, coupled with a percentage (generally 20-30%) of the organisation also having Office software, though not necessarily Office 365.  
  3. Set aside 12-15% extra budget for the existing E3 environment, plus a similar increase for support of the Office environment, and re-evaluate the situation in 2-3 years

IBRS also recommends considering what will happen in another 10 years, when many organisations have migrated to E5 (which is likely). What new business risks will emerge from this? Migrating from Office 365 E3 to a competitive product (e.g. Google or Zoho) is hard enough. When E5 features are fully leveraged, the lock-in is significant, but so too is the value. At the end of the day, the ultimate risk factor is trust in Microsoft not to engage in rent-seeking behaviour.

Related IBRS Advisory

  1. Pros and Cons of Going All-In With Microsoft
  2. Special report: Options for Microsoft support - Key findings from the peer roundtable: August 2020
  3. The journey to Office 365 Part 6: Mixing up Microsoft’s 365 licensing and future compliance risks
  4. DXC Technology and Microsoft collaborate on workplace experience
  5. AIP Should be Essential to Any O365 and Workforce Transformation Strategy
  6. AIS and Power BI Initiatives
  7. Microsoft Pivots to Target Verticals

The Latest

12 August 2021: TechnologyOne released a significant report based on a six-month long study into the economics of Cloud computing and SaaS among Australian organisations.  

The study, which was independently conducted by IBRS and Insight Economics, explored the tangible costs associated with migrating to the Cloud, with both IaaS and SaaS journeys investigated. An economic analysis of the data collected through 67 in-depth case studies with CIOs and C-suite executives, additional interviews, and over 400 respondents, revealed a $224bn economic dividend for the Australian economy, prompting TechnologyOne to term the report "too big to ignore".

Why it’s Important.

While the report is aimed at policymakers and strategies looking at the macro-economic impact of technology, it also details the costs and benefits of Cloud adoption by industry sectors, providing IT strategists with realistic benchmarks. 

When developing the methodology for the report, IBRS and Insight Economics took a ‘no free lunches’ approach to data collection. Unlike other reports on the benefits of Cloud migration, the study took into account the costs of, and time needed for transition, including training, change management, skills (and skill shortages) and the fact that many organisations will need to retain on-premise environments to support legacy and home-grown applications for years to come. In addition, only productivity benefits that had been measured were included in the analysis. 

As a result of the evidence-only approach to the study, the ‘direct returns’ on Cloud migration detailed in the report are both far lower and far more realistic than those found in studies conducted in the USA and Europe.

The report may be accessed here: https://toobigtoignore.com.au/

Who’s impacted

  • CEO, COO, CFO, CIO
  • Cloud migration teams

What’s Next?

The conservative approach to the study, the rich data collected, means that organisations still struggling to make a business case for SaaS have practical benchmarks and economic modelling to call upon.

Related IBRS Advisory

  1. The economic impact of software as a service in Australia
  2. Get board agreement to the Cloud strategy

The Latest

28 July 2021: During Inspire, Microsoft unveiled Windows 365, which it positions as a Cloud desktop service. IBRS views Windows 365 as an evolution of existing virtual desktop solutions. 

In addition, Windows Virtual Desktop services have been rebranded as Azure Desktop Services. With this rebranding, Microsoft also introduced a number of enhancements, including closer integration with Azure Active Directory (AAD) and Endpoint-Manager, with the ability to deploy applications across both physical devices and Cloud-based desktops based on roles. 

Windows 365 is built on top of Azure Virtual Desktop service. The difference between Windows 365 and Azure Desktop Services is that Windows 365 has more automated, easier deployment and administration options. It is well suited to organisations with minimal VDI specialisation and more akin to a ‘fully managed virtual desktop environment’.  

In contrast, Azure Desktop Services is better suited to larger organisations that have a need for a high level of customisation. It is more akin to a virtualised Citrix farm.

Why it’s Important.

In 2019, Microsoft quietly changed the licensing conditions for running virtual servers in the Cloud, which hindered VMware’s ability to migrate VDI (among other services) to hyper-scale Cloud services. Since then, IBRS has had reports of efforts to migrate VDI into the Cloud stifled by rights, with Microsoft partners steering organisations to an ‘all-in Azure’ approach.

The introduction of Windows 365 and the rebranding of Azure Virtual Desktop certainly fits a strategy of selecting alternative virtual desktop environments less compelling. 

This is not to say that Microsoft’s VDI capabilities are not solid offerings. Windows 365 certainly addresses a problem in the Australian market, where fully managed VDI has suffered greatly from vendors under-scoping the resources needed to run a client's environment in order to come in at the lowest possible cost. Autoscaling in the Windows 365 environment largely eliminates this issue. The level of automation is also impressive, as is an application cook

Who’s impacted

  • CIO
  • Development team leads
  • Business analysts

What’s Next?

Windows 365 is a viable option for specific use VDI cases, and it may be considered against traditional fully managed desktop vendor solutions. However, it may not be cost-effective at scale. Solutions from AWS, VMWare and Google should also be examined, though it is important to consider the total cost of operation of this type of VDI, not just the licensing / service costs. Be sure to factor in human resources for administration, application compatibility testing and packaging (which are significant hidden costs and often overlooked, as well as help desk and support.

In addition, if staying within the Microsoft stack, Azure Desktop Services can provide a more flexible and scalable solution. Again, be sure to factor in the total cost of operation.

Overlooked by many discussions of Cloud VDI is the rise of Cloud application virtualisation services from the likes of Cameyo. Rather than presenting an entire desktop, these services only stream a configured application, either in a manner that makes it appear as a native application or within a web browser. Such an approach is significantly lower cost than traditional VDI. When considering a new virtual environment for your workers, both VDI and Virtual Application Delivery (VAD) options should be considered.

Related IBRS Advisory

  1. Should You Outsource Your Virtual Desktop Infrastructure?
  2. When to Consider Virtual Desktop Infrastructure
  3. VDI trends for 2021–2025
  4. End-user computing managed services: 3 initial things to consider for the RFP
  5. SNAPSHOT: Workforce Transformation beyond Mobility and Digital Workspaces
  6. IBRS Compass: Beyond the Desktop: Creating a Digital Workspace Strategy for Business Transformation

To improve call centre resources scheduling, some organisations have implemented software agents to either improve users’ experience and/or reach the right expert at the right time. Organisations should assess the software agent maturity and determine which level should be reached to fulfil the business imperatives.

Log in and click the PDF above to download the 'Software Agents Maturity Model' infographics poster to discover:

  • 5 levels of software agent maturity
  • 9 qualifiers used to evaluate software agents
  • A self assessing approach to address software agent shortcomings