Shared Computer Activation for Office in Microsoft 365 Business
Published Apr 22 2019 10:10 AM 175K Views
Microsoft

We are excited to announce the ability to enable shared computer activation for Office by Microsoft 365 Business subscribers

 

Normally, users can install and activate the Office 365 Business Client only on a limited number of devices, such as 5 PCs. Using the Office 365 Business Client with shared computer activation enabled doesn't count against that limit.

 

This helps in scenarios where multiple users are connecting to the same remote computer at the same time. The users can each run Office programs, such as Word or Excel, at the same time on the remote computer. Enabling shared computer activation for Office can also be useful in situations where multiple users share the same computer and the users are logging in with their own account. A few examples of where Office with shared computer activation enabled could be useful are:

 

  • Three workers at a warehouse share a computer, each worker using Excel on that computer during their shift to track orders & shipments
  • Five nurses at an outpatient clinic use Word on shared computers at the nurses station throughout the day to create encounter reports from a template
  • The business owners, billing clerk, and the accountant connect remotely to a Windows 2016 Server running Remote Desktop Services (RDS) to use Excel and the company’s accounting software.
  • Field service employees use Office on a computer that's located in a conference room to update/write reports when needed.
  • Remote medical billing coders and auditors working from home connect to Windows Virtual Desktops (WVD) in Azure with Office installed to work on highly sensitive medical records.

 

Please refer to this article for how you can enable shared computer activation for Office.

 

Please note that the ability to enable shared computer activation for Office is a Microsoft 365 Business entitlement and not a feature of Office 365 Business in general. The roll out of shared computer activation for Microsoft 365 Business customers will begin 4/30 and we expect the roll out to be completed in the next couple of months.

69 Comments
Brass Contributor

Does this mean that M365 Business includes Pro Plus or just the activate rights?

Microsoft

@Mark Benton Just the activation rights in the existing business client that comes in M365B. It does not include Office 365 Pro Plus

Copper Contributor

Will this mean that if I have a shared computer activation instance of O365 Pro Plus already configured, that my M365B users will be able to sign in and activate it?  Or will I need to configure SCA on an M365B product?

 

Edit: Also, can you confirm if this will be available to M365 Business Premium users?

 

Thanks!

 

Copper Contributor

So, to be clear, we can now use Office from M365B on Terminal Servers deployed into clients, rather than having to buy Open Licence versions of Office for those servers/users?

Brass Contributor

Great News. This will help with migrating a bunch of our customers to Microsoft 365 Business.  How do we know if it's been rolled out to a specific tenant?

Copper Contributor

Anxiously awaiting this feature - I would also like to know how to verify when rolled out to a specific tenant and/or learn schedule if it is going to be a while. West coast US so hopefully soon. I have a client desktop deployment that's been frozen waiting for this.

Copper Contributor

Can we mix the Pro Plus with the M365B on the same RDS?
When will the Shared Activation be Enroled?

Copper Contributor

The Microsoft Online Service Terms dated May 2019 still appear to state this is not allowed?

 

https://www.microsoft.com/en-us/licensing/product-licensing/products#OST

 

Office 365 Applications
Office 365 Business
Office 365 ProPlus
Visio Online (Plan 1 and 2)

 

Installation and Use Rights
Each user to whom Customer assigns a User SL must have a work or school account in order to use the software provided with the subscription. These users:
• may activate the software provided with the SL on up to five concurrent OSEs for local or remote use;
• may also install and use the software, with shared computer activation, on a shared device, a Network Server, or on shared servers on Microsoft Azure or with a Qualified Multitenant Hosting Partner. A list of Qualified Multitenant Hosting Partners and additional deployment requirements are available at www.office.com/sca. This shared computer activation provision does not apply to Customers licensed for Office 365 Business; and
• must connect each device upon which user has installed the software to the Internet at least once every 30 days or the functionality of the software may be affected.
• may use Internet-connected Online Services provided as part of ProPlus. Additionally, if permitted by Customer, users may elect to use connected services subject to terms of use other than this OST and with respect to which Microsoft is a data controller, as identified in product documentation.

Microsoft
Thanks for flagging this. We are working with our teams to have the OST amended to include Microsoft 365 Business
Copper Contributor

Can somebody from Microsoft confirm the function to install with the Office Deployment Tool, Business Premium on a shared computer? An then Business premium users can activate and use the apps.  I just completed an install and it denied activating a Business premium user with an error message.   I made sure I pulled down the correct version of software (O365Business) with the deployment tool, not the Pro Plus version.  Should this have worked or is this feature not yet implemented for Business versions?

 

I have users that share the same computer (such as computer in a meeting room hooked to a large monitor) and some are E3 and some are Business Premium.  Can the E3 users activate with the Business Premium install since it's a lower level?  We just need the common apps like Word, Excel, Outlook and Skype for Business to authenticate.  These apps are the same between the license levels.  I have not yet found a way that both Business Premium users and E3 can share the same apps on the same computer.  Is there a way to do this?  Please post the instructions if so otherwise can you put it in as an enhancement?  Any higher license level should be able to activate with lower product install.  They just won't get some of the extra features of their higher license while using that particular computer. 

 

The other option that would be acceptable is with a Pro Plus(E3) install a Business Premium user can still authenticate to apps that are the same between license levels.  I have tried this today and this definitely does not currently work.

Copper Contributor

Update: I just uninstalled all O365 installs on a computer.  I then reinstalled using the Office Deployment Tool the O365Business package.  Thinking this would allow all my Business Premium users to authenticate.  This initially worked and the version was 1808.  I could also authenticate as E3 licensed user which was great, just what I needed. But then an update to Office 1904 came down and now the Business Premium users can not authenticate.  A message displays "The products found in your account cannot be used to activate office in shared computer scenarios".  However, an E3 user can still authenticate with no problem.  This is odd because E3 users fall under the Pro Plus version of Office and that's not the version installed.  Long story short is this shared computer activation stuff seems to only work for E3 and up licensed people or maybe also Pro Plus volume licensed people. If someone has been able to get shared computer use Office installs to work with O365 Business Premium licensed users, please let me know how you did it.  Technically it might not be supported or allowed, but it would be nice to have some clear documentation from Microsoft on this.  Why can't shared computer O365 activation work with Business Premium users?  It did when I had Office version 1808 installed.

FYI: the SCA Feature for M365 Business will not be available right away for all Tenants. As mentioned in the article: "The roll out of shared computer activation for Microsoft 365 Business customers will begin 4/30 and we expect the roll out to be completed in the next couple of months." Meaning it might take a while before SCA for M365 can be activated on your Tenant.

Copper Contributor

@Rogier_Honselaar Is there anyway to check a tenants status? Is there an update on how the roll out is going? Originally, Microsoft stated the roll out would begin mid-april then changed to April 30th. I just want to be sure the roll out actually began. I would hate for June to get here and Microsoft change the roll out again and say the roll out will be complete by Q4. I understand things happen, I just need Microsoft to have open communication so I can give an explanation to my bosses. They were hoping for this to be live by June. Thanks Guys!

Copper Contributor

@Dave Olson 

Update: I just uninstalled all O365 installs on a computer.  I then reinstalled using the Office Deployment Tool the O365Business package.  Thinking this would allow all my Business Premium users to authenticate.  This initially worked and the version was 1808.  I could also authenticate as E3 licensed user which was great, just what I needed. But then an update to Office 1904 came down and now the Business Premium users can not authenticate.  A message displays"The products found in your account cannot be used to activate office in shared computer scenarios".  However, an E3 user can still authenticate with no problem.  This is odd because E3 users fall under the Pro Plus version of Office and that's not the version installed.  Long story short is this shared computer activation stuff seems to only work for E3 and up licensed people or maybe also Pro Plus volume licensed people. If someone has been able to get shared computer use Office installs to work with O365 Business Premium licensed users, please let me know how you did it.  Technically it might not be supported or allowed, but it would be nice to have some clear documentation from Microsoft on this.  Why can't shared computer O365 activation work with Business Premium users?  It did when I had Office version 1808 installed.

This is NOT for "Office 365 Business Premium" but for "Microsoft 365 Business". So regardless of the roll out status, this won't work for Business Premium users

Copper Contributor

@Griffin Cash @Rogier_Honselaar 

I don't understand why this would not apply to O365 Business Premium as well since it is a higher tier license than O365 Business.  Why would E3 be fine and O365 Business, but not O365 Business Premium?  According to this link, both O365 Business and Business Premium use the same install package.

https://support.office.com/en-us/article/product-ids-that-are-supported-by-the-office-deployment-too...

 

If someone from Microsoft can clarify if this shared use will apply to all Business level licensing or not, that would be much appreciated?  The way I see it, if anything the O365 Business Premium would work and the O365 Business would not because it's a lower cost license. Why would Microsoft skip over O365 Premium for shared computer activation since it sits in between O365 Business and E3?

Copper Contributor

"MICROSOFT" is the keyword. MICROSOFT 365 Business , not Office 365 business

Copper Contributor

@Griffin CashThe applications are the same between the two from what I see, and according to the deployment tool link I provided, it doesn't even list Microsoft O365 Business as a separate installable package. In any case Microsoft is making it extremely confusing with it's naming of O365 products. The standard office apps between Microsoft O365 Business, E3 and Business Premium for the most part are the same.  So why would Microsoft say a fully licensed Word, Excel, Outlook, and Powerpoint user doesn't have the same right to run those apps on a shared computer?  What would be the logical reason to not apply this same shared computer usage to all business level licensed O365 users? 

Copper Contributor
Microsoft

@Dave Olson Shared Computer Activation feature was not an entitlement available in SMB skus previously - you had to purchase Office 365 E3 to get this feature. With this announcement, we've made Shared Computer activation feature available in Micrososft 365 Business which is our premium offering among SMB skus.

 

So to clarify among the SMB Skus, Shared Computer Activation is only available to Microsoft 365 Business subscribers and is NOT an entitlement in skus like Office 365 Business Premium, Business Essentials and Business

Copper Contributor

Here's my issue and why this policy either needs to be expanded to all Business level O365 user licenses or authentication for different license levels need to be able to coexist on the same computer.

 

We have two room based meeting computers where it's attached to a large screen on the wall.  Right now as it stands, E3 licenses users and Business premium users can't both authenticate and use the same installed Word or Excel.  Our staff are well within their 5 device licensed limit so it should be no problem to have them authenticate with these two room computers.  But they can't.  Why?  Because if you install either of the Business premium package or the E3 package the other licensed group can't authenticate.  One would think you could install the Business Premium package and E3 should be able to authenticate since Business premium is a subset of E3.  There is nothing Business premium has that E3 doesn't also have.  But this doesn't work either.  How can I get my legally under the limit licensed E3 and Business Premium users to use Word, Excel, Powerpoint and Outlook on the same computer?  This should be a trivial thing to allow and it would be such a huge convenience especially for companies that have multiple shifts of workers sharing the same computer, but they might have different license levels.  If this can somehow be done and someone has done it, please let me know the secret.

Copper Contributor

@Dave Olson What if you install both Office Business and Office ProPlus? From my understanding, it will use whichever that user is licensed for. It sounds like you are willing to use one of the 5 licenses.

 

But on a second note, I'm pretty sure this SCA feature is more aimed at RDS users from Microsoft's viewpoint. 

Copper Contributor

@Griffin CashI have already tried installing both E3 and Business premium packages last week. Both even showed up in the installed programs list in Windows 10.  However it did not allow both licensed groups to authenticate, only E3.  Also we have tried this with RDS as well and never could get it to work reliably there either. Followed very specific instructions from MS.  I had some consultants try the same thing and they also could not get it to work. That's why I was excited about this post as it potentially meant Microsoft was going to finally allow shared computer use for rightfully licensed people across different license groups.  But it looks like my hopes have been quickly dashed.  This was never a problem when using the standalone apps and volume licenses.  O365 in this respect has taken a step backwards.

 

There shoudn't be anything fancy necessary to allow this.  If I open Excel, it should just look at my license and see that I'm licensed for Excel and I'm not over my limit of devices and allows me to run it.  But instead, I think Microsoft looks at the package level installed and probably stops at the first one it finds in the registry of the computer.  If no match, then it errors out.

Brass Contributor

In the past I had some PC's with a shared computer account that users logged on to.  They could then setup different profiles in Outlook and retrieve their email while signed in on a shared PC wit the shared account.  Now with ADAL turned on in Outlook, they cannot do this anymore as the shared account allows users to open any of the other users mailboxes.

Is there functionality that resolves this so the user can continue to logon with a shared account, then safely open their own mailbox without the concern others can open theirs as well?

Copper Contributor

So today I added a M365B subscription to one of our tenant, installed office using ODT to a RDS server, verified using powershell that the sub has SCA enabled, it has.

 

Below can be run using the tenant admin account.

Connect-MsolService
$sku = Get-MsolAccountSku | Where-Object {$_.skupartnumber -eq "SPB"}     
if ($sku) 
{   write-host ($sku.servicestatus | Where-Object { $_.serviceplan.servicename -match "Shared_Computer_Activation" }).provisioningStatus  
}

 

Still no dice, get the following error message "The product we found in your account cannot be used to activate office in shared computer scenarios"

 

I did raise a ticket and hopefully the Support guy pushed a magic button (script to update SOP's) , Will re-test er later and update with outcome.

 

UPDATE: magic button pushed, still not working. Sigh..

 

 

Copper Contributor

 

Just tested again on my test RDS server. Appears to be working now!!!!! 

 

On mobile at the moment. Gonna test a few more things but appears all is working.

Copper Contributor

Would be great to know if anyone has this working. On our RDS farm I get tokens generated but each RDS server overwrites the last token. As far as I understand it is supposed to generate a token for each server?

Copper Contributor

@Craig Mann working for me as of yesterday

Copper Contributor

@Griffin Cash do you use have more than one RDS server? I'd be interested to know if you get multiple tokens if so? We had Microsoft support look at it but they could not tell us the problem

Copper Contributor

Working for me now, only tested on one session host so far.

 

I'm just sad that the edition of office doesn't support GPO's, which is a crying shame.

Brass Contributor

I see a lot of people trying to activate M365 Business on RDS but my question is whether this is supported in a hosted environment? Specifically Azure.

 

I know there is an exception made for Office 365 ProPlus to allow it to be used on RDS in Azure specifically and Tier 1 CSP Partners can use it in their hosted environments provided they meet a couple of terms but for everyone else you need a SPLA agreement.

 

What's the terms relating to using M365 Business with SCA in RDS on Azure?

Copper Contributor

When will the Microsoft Online Service Terms will be updated to reflect this change? In the OST for June it is still written, dass SCA is not allowed for Office 365 Business - and not mentioned that it is allowed for Microsoft 365 Business. Wondering where to find the right to use SCA with M365 Business at all in the Microsoft Product Terms?

Microsoft

Hi @Ashanka Iddya, our partners are facing consistent, reproducible failures when trying to deploy M365B Office to RDS environments: "This product can't be activated on a computer that uses terminal services..." (roughly translated).

I've asked them to post their steps, .xml files and Office Deployment Tool ODT logs here. Please watch for new posts.

Maybe we can get to the bottom of this?

thanks,

Dom

Copper Contributor

Hello @Ashanka Iddya ,
at one of our customers we have the problem that we can not install a Terminal Server capable Office version with M365B licenses via the ODT.

The actual installation is successful, only when starting the products it is pointed out that they are not suitable for shared computer activation.
As an administrative domain user, we run the following cmdlet "setup.exe /configure configuration_install.xml" and then log in with a licensed user. Then the message appears.

1.jpg

 

 

 

<Configuration>

    <Add OfficeClientEdition="32" Channel="Monthly">

        <Product ID="O365BusinessRetail">

            <Language ID="de-de"/>

            <ExcludeApp ID="Lync"/>

	    <ExcludeApp ID="Teams"/>

            <ExcludeApp ID="Groove"/>

            <ExcludeApp ID="OneDrive"/>

        </Product>

    </Add>

    <Display Level="Full" AcceptEULA="TRUE"/>

    <Property Name="FORCEAPPSHUTDOWN" Value="FALSE"/>

    <Property Name="SharedComputerLicensing" Value="1"/>

    <Property Name="PinIconsToTaskbar" Value="FALSE"/>

    <Logging Level="Standard" Path="%temp%" /> 

</Configuration>


As a workaround we now had to use O365 E3 licenses.

How does the Office package need to be customized to run M365B licenses on a terminal server?

Thank you
Florian

Microsoft

@FHochhard Thanks for posting this. Could you please also add the ODT logfiles so we can take a closer look? They should be in %temp%, or else wherever you specified them. Thanks! :thumbs_up:

Hello @FHochhard 

 

I just ran a test with the following steps:

 

  1. Installed a Win2019 Server VM in Azure and made it a DC
  2. Installed a Win2019 Server VM with RDS in Azure joined to AD
  3. Set up a new Microsoft 365 Business tenant
  4. Installed and configured Azure AD Connect on the DC
  5. Installed Office 365 Business using ODT on the RDS VM
    1. Command: setup /configure Configuration_M365B.xml
    2. Config generated at config.office.com
      <?xml version="1.0"?>
      
      -<Configuration ID="ab7750be-ffe5-44b2-ae73-b205697d3a7f">
      
      <Info Description="Contoso Office Install for M365 Business"/>
      
      
      -<Add ForceUpgrade="TRUE" Channel="Insiders" OfficeClientEdition="64">
      
      
      -<Product ID="O365BusinessRetail">
      
      <Language ID="en-us"/>
      
      <Language ID="de-de"/>
      
      <ExcludeApp ID="Access"/>
      
      <ExcludeApp ID="Groove"/>
      
      <ExcludeApp ID="Lync"/>
      
      <ExcludeApp ID="Publisher"/>
      
      </Product>
      
      </Add>
      
      <Property Value="1" Name="SharedComputerLicensing"/>
      
      <Property Value="TRUE" Name="PinIconsToTaskbar"/>
      
      <Property Value="0" Name="SCLCacheOverride"/>
      
      <Property Value="0" Name="AUTOACTIVATE"/>
      
      <Property Value="FALSE" Name="FORCEAPPSHUTDOWN"/>
      
      <Property Value="0" Name="DeviceBasedLicensing"/>
      
      <Updates Enabled="TRUE"/>
      
      <RemoveMSI/>
      
      
      -<AppSettings>
      
      <Setup Value="Contoso" Name="Company"/>
      
      <User Value="51" Name="defaultformat" Id="L_SaveExcelfilesas" App="excel16" Type="REG_DWORD" Key="software\microsoft\office\16.0\excel\options"/>
      
      <User Value="27" Name="defaultformat" Id="L_SavePowerPointfilesas" App="ppt16" Type="REG_DWORD" Key="software\microsoft\office\16.0\powerpoint\options"/>
      
      <User Value="" Name="defaultformat" Id="L_SaveWordfilesas" App="word16" Type="REG_SZ" Key="software\microsoft\office\16.0\word\options"/>
      
      </AppSettings>
      
      <Display AcceptEULA="TRUE" Level="Full"/>
      
      <Logging Level="Standard" Path="C:\odtLogging"/>
      
      </Configuration>
    3. After logging in using a UPN of a user, Office 365 Business with SCA worked properly
    4. SCA.png
    5. Have a look at your ODT logs.
      1. The key is to look for the Click-To-Run General Telemetry entry in your ODT log and find the SharedComputerActivation entry and make sure it is set to 1.  Here's an example from my install:

         

        11/27/2019 05:45:56.670           SETUP (0x4f0)              0x1534               Click-To-Run General Telemetry          aoh9t    Medium              TryLaunchClient::HandleStateAction {"MachineId": "16d801558d61f149b5521b69f7ac30cf", "SessionID": "711f1e86-31fb-47b6-9184-a14c20de4e90", "GeoID": 244, "Ver": "16.0.12228.20290", "C2RClientVer": "0.0", "ContextData": "{\"message\":\"Launching executable\",\"ClientExeName\":\"OfficeClickToRun.exe\",\"Parameters\":\" deliverymechanism=64256afe-f5d9-4f86-8936-8840a6a4f5be platform=x64 productreleaseid=none devicebasedlicensing=0 forcecentcheck= culture=en-us defaultplatform=False lcid=1033 b= storeid= forceupgrade=True piniconstotaskbar=TRUE forceappshutdown=FALSE autoactivate=0 totalclientcabsize=27453976 productstoadd=O365BusinessRetail.16_en-us_de-de_x-none scenariosubtype=ODT scenario=unknown updatesenabled.16=True acceptalleulas.16=True cdnbaseurl.16=http://officecdn.microsoft.com/pr/64256afe-f5d9-4f86-8936-8840a6a4f5be version.16=16.0.12228.20290 sclcacheoverride.16=0 mediatype.16=CDN baseurl.16=http://officecdn.microsoft.com/pr/64256afe-f5d9-4f86-8936-8840a6a4f5be sharedcomputerlicensing.16=1 o365businessretail.excludedapps.16=access,groove,lync,publisher sourcetype.16=CDN flt.useexptransportinplacepl=unknown flt.useoutlookshareaddon=unknown flt.useofficehelperaddon=unknown\"}"}

 

Hope this helps!

 

David

Copper Contributor

Hello @David Bjurman-Birr,
many thanks for your help!

It worked with the latest ODT-version and your configuration xml.
Now it can be activiated with M365B licensed users.

Also many thanks @Dom Cote for your help and support!


Kind regards
Florian

Copper Contributor

Hi @David Bjurman-Birr 

 

Do you still need license for RDS itself? I have not been keeping up with recent RDS changes, but this M365B feature sounds interesting.

Can you provide documentation on your test ‎on ‎11-26-2019. I like to set up a test environment to play with this.

 

Thanks!

Brass Contributor

@David Bjurman-Birr 

 

Many thanks for that config, resolved our RDS BCDR server issue perfectly.

Copper Contributor

I hit a snag. I'm getting the error "The products we found in your account cannot be used to activate Office in Shared computer scenarios."

Dave Olson mentioned and then got beat up about it for no reason. His response was valid if it's correct:

Our licenses are Office 365 Business Premium. Are Premium customer not allowed to use this on a shared device then? Seems silly if the "Business" version can.

 

If that is the case, what is the alternatives to installing office on a shared Remote Desktop? 

 

Venting The link for any of the documentation talks about ProPlus. There's so much documentation I've been getting irritated at even creating this config file from config.office.com  At one point I had 6 different documents open talking about the steps/options, yet all of them were not in a complete comprehensive order on just installing the dang software correctly. 

Copper Contributor

Thanks for the support on this ITKNS.  Now that Microsoft is changing their Office product naming and license naming I wonder if they will change the shared use ability too.  We have a shared computer in a meeting room people use for video meetings.  MS Teams works fine, but the other office 365 apps don't if the person logging in has a different license from what is installed on the shared computer.  We have some people with E3 licenses and some with Business Premium.  I understand if the license includes other applications that those wouldn't be available, but the BASE versions of Word, Excel, Outlook and PowerPoint should all be treated the same. I do understand there are some enhancements available to the higher license, but upon login, I would think those could just be disabled for that users session.  Or at least have the option to install the lower tier base version of those apps that would work for E3 people as well.  It doesn't make sense we would have to put all our people at the E3 level just so they can run those BASE apps which are included in both licenses.

Brass Contributor

We are running Microsoft 365 Business Premium (New Name) on a couple dozen customer RDS servers and shared computer activation is working great.  You can install Office 365 Business on and RDS server using the ODT, but we have found it will activate office on servers that have Pro Plus installed by the ODT. Just make sure you include that shared computer activation flag. Microsoft 365 Business Premium is the best bang for your buck SKU Microsoft has ever created. Incredible value and they are adding Azure AD Premium P1 to it. 

Copper Contributor

So am I to understand that the installation of a single Microsoft 365 Business Premium license on a a shared computer will work for people who sign in with E3 or O365 Business Premium license?  Right now we have the shared computer installed with an E3 license ($20 per month) and the apps complain if a person with a O365 business premium license ($12.50 per month) logs in.

Brass Contributor

Office 365 Business Premium (now called Microsoft 365 Business Standard) is not supported in RDS/Shared Activation scenarios. You need the $20 E3 or the $20 Microsoft 365 Business Premium to use Shared computer activation.

Microsoft

Hi @ITTKNS @Dave Olson

 

Shared computer activation is an M365 Business entitlement. It is not available with Office 365 Business Premium. If you're using shared computer activation, the user or users have to be  appropriately licensed for it. Using one license of  M365B and having users On office 365 BP utilize that benefit is a violation of licensing terms

Copper Contributor

Do they sell shared keys instead for Remote Desktops so anyone can use it and they don't have to sign into the product? Just seeing if there's different options besides changing end users licenses. Not sure if that would conflict? 

 

Venting again The licencing Structure for this is confusing. Microsoft 365 Business Premium and Office 365 Business Premium are too close in naming. Microsoft should change the names so they are not so close. I set all this up and found out the hard way we don't have the right licenses after 2 days of setting all this up. 

Brass Contributor

If you want to use shared keys on RDS than Open License is the way to go.

Copper Contributor

Odd. If I go to the Office 365 Admin website to compare services, business definitely does not show the capabilities for Remote Desktop. Since this blog is almost a year old, I would suspect someone either forgot to check the box or this is not capable? I also got an email that the naming scheme was being changed. We must not be the only ones confused.  

Screenshot_4.jpgScreenshot_3.jpg

Microsoft
Hi Nikole, Thanks for the screenshot. That's a miss on our part. Microsoft 365 Business does have Shared computer activation and WVD. Please refer to the detailed licensing comparisons for more details: https://docs.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/li...
Copper Contributor

@Ashanka Iddyadoes that mean that Microsoft 365 Business Standard will also have SCA?

Microsoft

@RYC-KLC 

 

SCA is only available in Microsoft 365 Business Premium ( or old name Microsoft 365 Business). It is not available in Microsoft 365 Business Standard (or old name Office 365 Business Premium)

Version history
Last update:
‎Apr 22 2019 10:10 AM
Updated by: