Bezoek een het Nieuwe Werken sessie - Microsoft | Het nieuwe werken

Bezoek een het Nieuwe Werken sessie - Microsoft | Het nieuwe werken

Bring Your Own App (BYOA) storming Australian businesses, IT departments ill prepared to manage the change

March 11, 2014  |   Announcements

Nearly two-thirds of Australian enterprises now have staff that use personal apps for work, or Bring You Own App (BYOA), and businesses are struggling to keep up with this phenomenon which is set to overtake BYOD as a strategic IT change, according to a new study released today by emerging technology analyst firm Telsyte.

Telsyte’s Australian Enterprise Mobility Market Study 2014 surveyed more than 460 CIOs and ICT decision makers on their organisation’s approach to BYOD and BYOA . The findings revealed 27% of organisations allow staff to use any personal mobile or cloud app for work purposes without any restrictions.

A similar number allow BYOA from an approved catalogue of apps and a smaller set of businesses do not allow it, but CIOs concede staff go ahead and do it anyway. Among companies that allow, or tolerate, BYOA, 30 per cent of staff actively use personal apps for work purposes indicating a high groundswell of interest.

Some 34 per cent of businesses do not allow BYOA at all and enforce it with tactical approaches like management tools or other means.

Telsyte Senior Analyst Rodney Gedda says there is a lot of interest in the BYOD trend, but many organisations have overlooked the apps that enter the workplace on personal devices.

“Couple this with thousands of mobile apps, for both personal and business handsets, and the plethora of cloud services available via mobile devices and the Web, and people are creating a new form of shadow-IT with BYOA,” Gedda says.

According to Telsyte research, popular BYOA software used for business include: data backups and storage (Dropbox, iCloud); calendaring; collaboration (GoToMeeting, WebEx); voice communications (Skype); project and task management (Remember the Milk); productivity (Pages, QuickOffice Pro); multimedia; and note taking (Evernote).

Balance BYOA for productivity and security

Local businesses can take advantage of the emerging BYOA trend by allowing staff to be productive with public software, however, in many cases this will need to be balanced with the security and integration requirements of corporate IT.

If businesses ban BYOA outright they will miss out on productivity and innovation that comes with people managing their own IT requirements.

Telsyte research indicates data privacy and security are the number one challenges cited by CIOs arising from staff adopting “Bring You Own” IT – both devices and apps.

Nearly 80 per cent of Australia’s IT departments have no plans to officially support BYOA further indicating the lack of readiness for this emerging social trend.

Summary of report findings

• Smartphones are the preferred business device with 80% of existing organisation-owned mobile handsets being smartphones.
• 84% of organisations have ICT and processes in place for people to become a mobile worker.
• 44% of organisations currently support BYOD and is set to grow rapidly with 34% of organisations that currently do not support BYOD, planning to adopt within in two years.
• Email access was the number one factor driving BYOD. Data privacy and security are the top challenges with BYO cited by ICT decision makers.
• Bring Your Own Apps (BYOA) now in two-thirds of businesses, IT departments largely unprepared for this change.
• Around a quarter of Australian businesses currently use a dedicated MDM solution, more than doubling in 12 months.
• The MDM vendor space remains fragmented with BlackBerry the most implemented followed by AirWatch, MobileIron, Good Technology and SAP.

About the Telsyte Australian Enterprise Mobility Market Study 2014
The Telsyte Australian Enterprise Mobility Market Study 2014 is a comprehensive 85-page report, which provides subscribers with key market insight across mobile service provider market share; mobility strategy; device purchasing trends; supported mobile operating systems; smartphone brand penetration; factors influencing smartphone purchasing; mobile e-mail; BYOD; BYOA; media tablet market share and impact on PCs; mobile app development; apps used on smartphones and media tablets; mobile device management (MDM); mobile application management (MAM) and enterprise wireless (Wi-Fi).

Will Microsoft enter the DaaS market fray with Mohoro?

Microsoft has a lot to lose if it doesn't join the Desktop as a Service market.

Gabe Knuth wrote a lot about Microsoft licensing, focusing on the fact that no matter how you slice it, Microsoft is making our lives miserable. This is especially true for DaaS providers, since Microsoft doesn't allow them to share compute resources (called multi-tenancy) with multiple clients. Each piece of compute hardware (and, if you ask some people, storage) must be designated for a single company. That results in excess processing capacity going to waste that could be used to realize vast economies of scale. Not only is it inefficient, it's also maddening that Microsoft arbitrarily restricts something that is technically possible.

Ultimately, it means that DaaS costs more than it has to if you want to deploy Windows client operating systems. To combat this, DaaS providers are using single-user Remote Desktop Session Host (RDSH) servers, which aren't governed by the same asinine restrictions because you simply need to buy a per-user RDS client access license for each user. Plus, there is a service provider licensing program for RDSH servers, which means they can share any resource they want among their clients. This practice is catching on at service providers and within organizations, and the very fact that we have to do this is the catalyst of the #fixvda movement.

Musing Microsoft's Project Mohoro

Imagine, then, the reaction of DaaS providers to hear rumors of Microsoft's Project Mohoro. Mohoro is expected to be Microsoft's own DaaS offering, hosted in Azure. Rumors circulated back in May, and while there hasn't been any more information emanating from Redmond, the DaaS market is shaping up so that if Microsoft doesn't have an offering for its own OS, it will be left behind.

Citrix has one. VMware has one. Dell, well, theirs was based on the Desktone platform that VMware now owns, so we'll have to wait and see on that front. The point is that Microsoft, the company with the most to gain from a DaaS tool as well as the most to lose if people move off Windows, needs to be in this landscape.

MORE ON THE
DAAS MARKET

What customers need to knowabout DaaS

How are DaaS and VDIdifferent?

FAQ about Desktop as a Service

But what will Mohoro look like? Will it be RDSH-based, usingsome version of Windows Server? If so, which version of Server? Some use cases still require 16-bit applications. Will you be able to run Windows Server 2003 R2 or Windows Server 2008 R1? Despite those questions, the RDSH method is the easiest, because running Windows 7 or 8 would be complicated due to the licensing restrictions Microsoft itself imposes.

In July, Microsoft amended its licensing agreement for Azure to expand the use of Remote Desktop Services (RDS) in Azure virtual machines beyond admin tasks. RDS is an umbrella term that includes RDSH (terminal services) and Remote Desktop Virtualization Host (VDI), but Microsoft was careful to note that client versions of the OS are still not able to be used due to the multi-tenancy restrictions.

All this adds up to RDSH being the most likely candidate. When it was first rumored, Mohoro was called RemoteApp as a hosted service, which would indicate seamless Windows apps delivered from Azure. Still, all the news related to this came out between May and July. There are new indicators that DaaS's stock is rising, so could there be more to this?

Microsoft licensing's gotta give

As long as Microsoft plays by its own licensing rules, no new complaints should arise aside from partners squawking about stealing customers. If, however, Microsoft decides that since it owns the OS it can make up its own rules, you can expect an IT donnybrook to break out. The idea most talked about would be that Microsoft can escape its own licensing limitations by creating another version of Windows that is virtually identical to a client version of Windows and license it only to itself. That theory likely draws most of its supporters from a pool of people that are known to wear tin foil hats, but it is possible.

What it means, though, is that if Microsoft is going to play in the DaaS market and not just deploy applications, something will have to give. Microsoft will either have to fully back the single-user RDSH method (which simply has to cost them money compared to selling client OS licenses), make changes to Windows client OS licensing, or do something more drastic like creating an OS for its own use only.

Rumors of Project Mohoro persist, so I expect it to happen, but exactly how disruptive it will be remains to be seen. If it's just RDSH from the cloud, it will be simply another deployment option. If it's more than that, it will be very interesting to see how things shake out in theevolving DaaS market.

Mohoro

Forse stijging claims illegale software

Bedrijven die hun netwerk niet actief scannen op software zonder licenties zijn vogelvrij in de huidige Nederlandse rechtspraktijk. De Business Software Alliance (BSA), een lobbygroep van softwarebedrijven die piraterij bestrijdt, meldt juichend dat het boetegeld dat zij vorig jaar in Nederland wisten op te halen met claims rond illegaal gebruik van software fors gestegen is.

Dit claimbedrag dat Nederlandse organisaties betaald hebben omdat er in hun ongelicentieerde software in Nederland is in 2012 met 56 procent gestegen ten opzichte van 2011. De schadeclaims kwamen in 2012 in totaal uit op 3,2 miljoen euro, terwijl dit in 2011 nog 2 miljoen euro was. De BSA stelt dat Nederlandse bedrijven de hoogste boetes betalen voor het gebruik van ongelicentieerde software van alle landen in de Emea-regio in 2012. In de claimsom zijn advocatenkosten overigens niet meegenomen. Dat kost ook een lieve duit.

De BSA stelt dat de bedrijven waar ze via de rechter met succes een claim afdwingen lang niet altijd opzettelijk illegale software gebruiken. De Nederlandse rechter is toch onverbiddelijk in dit soort gevallen: gebruik van illegale software wordt als schending van het intellectueel eigendomsrecht gezien waaraan forse schadeclaims hangen. De BSA houdt het niet op de relatief strenge handhaving van het auteursrecht, maar suggereert dat er in Nederland opzettelijk relatief veel illegale software gebruikt zou worden. “Het is alarmerend om te zien dat het gebruik van ongelicentieerde software bedrijven in Nederland meer kost dan in elk ander land in de Emea-regio”, zegt Julian Swan, director of compliance marketing BSA Emea. “Dit zou een indicatie kunnen zijn van een bovengemiddeld gebruik van ongelicentieerde software in Nederland.”

Wie zijn bedrijfsnetwerk niet actief scant op software waarvan de licenties niet netjes betaald zijn, is het haasje. De BSA haalt het voorbeeld van een Nederlands bedrijf aan dat vorig jaar maar liefst een claim van ruim 4 ton euro aan zijn broek kreeg omdat er illegale software aanwezig was op het netwerk. De BSA raadt bedrijven dan ook aan om meer energie te steken in het beheer van software, het zogenaamde software asset management. En dan nog even een preek van de BSA dat het licentiegeld niet een investering is die je om niet over de balk smijt: “bedrijven moeten software meer gaan zien als een strategisch bedrijfsmiddel dat ze helpt producten te ontwikkelen, diensten te leveren, interne werkzaamheden uit te voeren en zaken te doen”, aldus Swan. Nederlandse organisaties wees vooral gewaarschuwd: de jacht is geopend en dankzij de Nederlandse rechter schiet de BSA raak!

The Microsoft Cloud Power eBook

The Microsoft Cloud Power eBook will give you a clear-eyed view of your options in the cloud. In this quick read—full of valuable videos, case studies, and white papers—we'll show how you can protect your data and applications in the cloud. And we'll explore how you can move to the cloud on your terms by extending your current infrastructure.

The Microsoft Cloud Power eBook

Office365 Dual Use Rights

Summary:  If you deploy workloads into Office 365 and maintain existing on premises workloads, or in some cases, deploy additional on premises servers to support a hybrid configurations- how do you maintain access to on premises servers.  It really doesn’t matter if your long term goal is to move to the cloud entirely, or maintain a hybrid configuration going forward – the licensing is the same.  In this Licensing How To post, we cover a concept sometimes called “on premises access rights,” “dual use rights”, and “on premises use rights.”  There really isn’t an official term, but the overall use right is to leverage your Office 365 licenses to access on premises servers, instead of buying CALs.

The Licensing How To series posts are provided by our Customer Service Presales and Licensing team members.  These scenario based licensing topics are written on trending topics and issues based on their interactions with customers, Partners and field sellers.  For more posts from the Licensing How To series, search the “Licensing How To” tag on this blog.
A frequently asked Office 365 licensing question that we address on our Team is: what happens if I buy Office 365 but continue to run on premises workloads for certain products? We’ve seen Office 365 Community Forums and other sites light up with something called “dual use rights,” “on premises use rights,” or “on premises access rights.” What does this mean, and how does it apply to me?  Well, the short answer is, it depends.  The basic licensing concept is if you’ve purchased a User Subscription License (User SL, or USL) for an Office 365 Service, that user is licensed to access the equivalent workload(s) running on premises.  While the applicable application server CALs are not included in the Office 365 User  subscription License, a CAL equivalency use right is included to access the on premises application server. 
At a high level, it works like this: Users licensed for applicable/eligible Office 365 services have use rights equivalent to a CAL for the purpose of accessing equivalent on premises workloads.  For example, a user licensed for Exchange Online Plan 2 can use their USL to access Standard and Enterprise CAL features of an on premises Exchange Server.  Below is a table with the three Office 365 services which have “on premises access rights.”  On the left and center columns we listed the on premises product and CAL type.  On the right column, we note the Office 365 User SL with rights equivalent to the on premises product and functionality.

On Premises Product	On Premises functionality	Office 365 User SL equivalent
Exchange Server	Standard CAL	Exchange Online Plan 1 User SL Exchange Online Plan 1G User SL Exchange Online Plan 2 User SL Exchange Online Plan 2A User SL Exchange Online Plan 2G User SL Office 365 Enterprise E1-E4 User SL Office 365 Education A3-A4 User SL Office 365 Government G1-G4 User SL
	Enterprise CAL	Exchange Online Plan 2 User SL Exchange Online Plan 2A User SL Exchange Online Plan 2G User SL Office 365 Enterprise E3-E4 User SL Office 365 Education A3-A4 User SL Office 365 Government G3-G4 User SL
SharePoint Server	Standard CAL	SharePoint Online Plan 1 User SL SharePoint Online Plan 1G User SL SharePoint Online Plan 2 User SL SharePoint Online Plan 2A User SL SharePoint Online Plan 2G User SL Office 365 Enterprise E1-E4 User SL Office 365 Education A3-A4 User SL Office 365 Government G1-G4 User SL
	Enterprise CAL	SharePoint Online Plan 2 User SL SharePoint Online Plan 2A User SL SharePoint Online Plan 2G User SL Office 365 Enterprise E3-E4 User SL Office 365 Education A3-A4 User SL Office 365 Government G3-G4 User SL
Lync Server	Standard CAL	Lync Plan 1 or 1G User SL Lync Plan 2, 2A or 2G User SL Lync Plan 3, 3A or 3G User SL Office 365 Enterprise E1-E4 User SL Office 365 Education A3-A4 User SL Office 365 Government G1-G4 User SL
	Enterprise CAL	Lync Plan 2, 2A or 2G User SL Lync Plan 3, 3A or 3G User SL Office 365 Enterprise E1-E4 User SL Office 365 Education A3-A4 User SL Office 365 Government G1-G4 User SL Live Meeting Standard User SL Live Meeting Professional User SL
	Plus CAL	Lync Online Plan 3, 3A or 3G User SL Office 365 Enterprise E4 User SL Office 365 Education A4 User SL Office 365 Government G4 User SL
Please note that applicable CAL Suite Bridge licenses may be required for on premises access  to workloads not included (i.e. Windows Server) in the Office 365 User Subscription License,  see the applicable product specific sections in the Product Use Rights document

A few important notes to mention before closing: 

• The plans listed above are the only current Office 365 licenses with “on premises access rights.”  Other Office 365 Plans, such as the Small/Midsize Business and Kiosk Plans do not have the same use rights.
• You are responsible for licensing the on premises server instances under their traditional license models.  For example, if you have 4 instances of SharePoint Server running on premises, you will need to have 4 licenses for SharePoint Server, as well as the underlying Windows Server licenses and applicable Windows Server CALs.
• Due to software license dependency, your Office 365 licensed users are still required to be licensed with underlying and supporting products – such as Windows and/or SQL Server CALs.
• Your Office 365 User SLs (as covered above) can be used to access your licensed servers deployed on third party shared servers/datacenters via License Mobility through Software Assurance.
• “On premises access rights” work for current versions of the above server products, as well as earlier versions (licensed or via downgrade rights)
• Office Web Apps Server has similar rights, where users licensed for Office 365 Plans which contain Office 365 ProPlus have rights to edit using an on premises Office Web Apps Server.  See our How to license Office Web Apps Server post for more details.

This is one scenario and licensing situation. Each customer scenario can vary by deployment, usage, product version, and product use rights.  Always check your contract, and the current Products Use Rights document to confirm how your environment should be fully licensed.  The blogging team does not warrant that this scenario will be the right licensing solution for other similar cases.

Works with Office 365 - Identity program

The Works with Office 365-Identity program

The Works with Office 365-Identity program provides testing and qualification of third-party identity providers with Office 365. Office 365 uses Windows Azure Active Directory for identity management and through this includes directory synchronization and federation. Microsoft supports Office 365 for customers who are using Office 365 with a federated identity provider that is qualified under the Works with Office 365-Identity program. Identity providers that have not been tested by Microsoft  are not qualified for federation with Office 365.

If you're an Office 365 customer, you can use an identity provider that is qualified in the Works with Office 365-Identity program and know that Microsoft has tested the configuration and that it will be able to support Office 365. Please note that for information about configuring or troubleshooting the third-party identity provider you should contact the third party instead of Microsoft.

The Works with Office 365-Identity program is currently focused on WS-* identity providers. These providers use one of the following two protocols:

• WS-Federation is the protocol used to support sign-in to Office 365 using the web interface, sometimes known as "passive authentication." This includes the Office 365 portal, SharePoint Online, Outlook Web Access, and the Office Web Apps.
• WS-Trust is the protocol used to support sign-in to Office 365 using Office client applications, sometimes known as "active authentication." This includes Outlook, Lync, Word, Excel, PowerPoint, and OneNote.

SAML-P and Shibboleth are alternative protocols to the WS-* protocols, and they provide sign-in support for web applications that is similar to WS-Federation. In some cases SAML-P and Shibboleth can also be used to sign in to Outlook using the Enhanced Client or Proxy (ECP) extension. Sign-in to Office 365 from other Office client applications is not possible with SAML-P or Shibboleth.

Qualified Works with Office 365-Identity partners are listed below, according to the protocols they use.

 Identity program