Is it possible to create new users and licenses to Office 365 using Azure Active Directory Powershell v2?
One of our services require Excel to be running on the server (I know Microsoft don't support Excel running on the server-side, but it currently works decently enough).
We're trying to automate the provisioning of these servers since it's currently a manual process - mainly around create new users / licenses for Office and activating Office.
I've managed to connect to the Office 365 account using Azure AD for Powershell (note that we don't actually use Azure, everything is hosted on AWS) and can see all the different users, groups, etc, however I have no prior experience with this, and am looking for any guidance on the how to achieve the following via Powershell:
create a new user
assign a new Office license for that user
activate Office with that new user
Yes, thats possible. But need to user the MSOnline Powershell Module. Here you have Set-MSOLUserLicense to assign licenses.
Related
I want to migrate my client's environment from drop box to SharePoint Online without using third party tools.
Can somebody guide me through the free tools that are available and also which other approaches exist.
I tried using Migration Manager creating drobox account however I am getting below error.
Just to clarify upon your issue, I opened up a free account in DropBox and I tried to create a connection within the Migration Manager Service, as it is described in the documentation.
I also got the error that you had:
Based on which I believe that it is required of you to have purchased an Enterprise Dropbox Account and that the free edition of DropBox is not supported, since you need an account that will be Dropbox administrator account to link with your Microsoft 365 migration.
As an alternative you could sync the DropBox Account Contents onto a File Storage and set up a Migrations Manager File Share Connection in order to upload all of the contents.
I have created an office add-in within visual studio code, I have published it on my Azure Storage Account, and via Centralyzed Deployment I've managed to install it for some users. The problem is that this add-in must be used by some clients, and there is no possibility that they'll use the addin stored in my azure account, and there is no possibility that they will create an account for me on their organization, in order for me to push data directly on their organization's azure account.
So what are the options? I need a solution where i send the office add-in as a zip or something like that, and the company's admin can easily upload that to its Azure account, and the manifest will point to their location. I've seen the possibility of downloading the addin from azure via ftp (without success yet), I imagine if i download that, there might be an option to upload for the client's company admin. Or am I on a wrong track?
many thanks!
I am trying to develop an application which uses the office 365 APIs .
I have created an Azure Directory and created an native client application.
When configuring my application there was an option to give permissions to other applications i need to use office 365 exchange application .
When I try to add that application to azure AD it says it costs 300 $.
Is there a way to use it as a trial one ???
I am not getting the office 365 exchange online option . What should i do?
That's not expected. It sounds like maybe it was trying to add the service to your subscription, rather than permissions. Can you provide a screenshot?
You may want to try this guide for registering:
https://github.com/jasonjoh/office365-azure-guides/blob/master/RegisterAnAppInAzure.md
I'm try to develop a Windows 8.1 App Store Application.
But i facing an issue how to integrate Office Automation with it.
Can someone advise me how to do Office Automation for Windows 8.1 App Store Application.
Firstly create an Office developer account.
In Solution Explorer by selecting Add->Connected Service select office 365 dont select files as you would require an OneDrive for Business account. Once signed in with Office 365 credentials, adding a service to the project is as easy as selecting the appropriate service and applying the required permissions.
Visual studio will now start adding the required files.
I have a Web application which will be deployed to Windows Azure and I'm looking for alternatives to generate Excel spreadsheets.
Can I use VSTO to programatically generate an Excel spreadsheet in a Web Role running on Windows Azure?... If yes, how should I deploy the application to Windows Azure? What assemblies should I include?
Joni and Joe are correct. VSTO will not run on Azure.
I believe you're looking for the Open XML SDK. That lets you create Excel or other Office files from .NET without using Office automation.
Edit: Here's one option I have considered for those times when the Open XML SDK just doesn't have the functionality I can get from accessing an Office app's object model directly. Set up a machine outside of Azure that operates just as an Azure worker role would by processing messages from an Azure Queue. Since the app on that machine could be setup to execute tasks sequentially, you should be able to get away with things that wouldn't be advisable if you were trying to execute an Office app from a web role. This machine could be in your data center, or you could use an Azure VM so that you could install Office. If that VM was creating and/or reading Excel documents, then just use Azure Blob storage to store the documents.
If the machine running Office is outside of Azure, you will incur additional bandwidth costs for all the data coming in and out of Azure.
I tested this and apparently it won't work, VSTO requires Office to be installed.
I've been successful with generating Excel Spreadsheets in Azure using EPPlus open source project. It builds on the OpenXML SDK, but is much simpler to use.
I've been deploying the code to Worker Role instead of Web Role (as per Lokad.CQRS for Azure architecture) in order to pregenerate reports, so that the application would be more scalable. And the only required assembly was the Epplus.dll.