sharing an office add-in to the client - azure

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!

Related

Drop box to SharePoint online migration without using third party tools

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.

OneDrive to trigger an Azure Function upon file sync

Azure and OneDrive friends,
I have the following usecase and need your help! Imagine there is an organization with Office 365 accounts and more specifically - the users utilize OneDrive, synchronized to local folders. We have a separate system running on an Azure environment. Is there a possible way whenever a file from any of the users is created / edited / synced in their local drives and respectively uploaded to the OneDrive... drive to trigger an Azure Function that lives in the Azure Environment from above?
Is there a way to set such triggers for all users (~150) from within an admin account?
Regards,
Borislav Nanovski
Yes, it is possible, but I´d use a Logic App with the OneDrive connector in Azure: https://learn.microsoft.com/en-us/azure/connectors/connectors-create-api-onedrive
I agree with #Jesus Hernandez. Use a Logic App that has a OneDrive trigger.

Unsure how to make an Azure AD app registration that can have its own onedrive folder

I am working on a project that needs to have a Onedrive folder that it owns where it can store and edit certain files. This folder also needs to be accessible through Onedrive to certain users in my organization.
I have created an App Registration in Azure AD, but can't figure out what permissions and configuration I need to achieve this. I know I can give it access to authenticate to a user and edit/create files on their behalf, but I don't want the folder/files to be associated with any particular user in the organization. How can I achieve this?
You might try creating and managing items using application credentials. Also take a look to permissions and shared for more information about making it accesible to others.
Are the files you're looking to store files that are visible to users or that are "data files" for your app? We don't currently recommend building apps that only store their own proprietary files rather than operating on visible user data. (It's a little more nuanced situation when you look at lists rather than libraries of files).
In general files that are expected to be shared among users without a single user owning them would be placed in a SharePoint site. You can then manage the permissions of the site to give access to the users that need the files. OneDrive for Business is specifically intended for files owned by an individual user.
At the moment we don't have provisioning APIs available through Microsoft Graph to create a site programmatically today, but you can look at the PnP Provisioning Engine for how to automate the process with legacy APIs, or if you really just need a single site you can create the site manually and then refer to it from your application.
The Drive API is the same whether you're accessing a OneDrive for Business or SharePoint site.

Is there any way download source code from "cloud services" in Windows Azure?

I don't have the latest version of the code deployed in the company's Windows Azure account, and I need to provide a fix to it. I know this can be done with "Azure Web Sites", but I'm not sure it's possible with "Azure Cloud Services".
Can anyone help?
If you did git deployment of the cloud service, you could fetch from the remote the same way you could with Windows Azure Web Sites. You may have updated the cloud service by uploading the package to blob storage first, in which case you could get the package. But, the package is not source code.
From a process perspective, you should label your deployments with a tag that can be matched in source control. You never know when a "hotfix" needs to be added to a branch off of the current production code.
In Windows Azure Cloud Services, instances are uploaded in the form of .cspkg packages.
According to the documentation, the Get Package operation retrieves a cloud service package for a deployment and stores the package files in Windows Azure Blob storage.
You could then download and extract this package (it is in ZIP file format) to retrieve its content. See this answer for more details.
In the case of ASP.NET applications, that will be a mixture of text files and binary assemblies (.DLLs). In the case of Java, it will be .jar files. You could use the appropriate decompiler to retrieve an approximation of the original source code. But it probably wouldn't be safe to change this reverse-engineered source code and upload it back into production, at least not without extensive testing.
yes. you can download it with an ftp client.
Ggo to dashboard of your site on https://manage.windowsazure.com.
Get credentials (username , password, host) and connect with you preferred ftp client.
Well, Azure now had a new portal and things are bit different. I had to retrieve the code for one of my websites.
To download the code,
go to App Service. In Overview panel, download publisher profile.
Now go to Deployment credentials panel. Enter the username for FTP and choose a password.
To connect to ftp, you need the URL from publishing profile (example.PublishSettings).
Now fire up your FTP client (FileZilla in my case) and put the FTP address and put the username like sitename\ftpusername (example\ftp-exmaple-user for me) and put in the password you choose in Deployment credentials panel.
wwwroot contains your code!
I realize it's an old question, in case anyone else needs it... I use the Cloud Explorer in Visual Studio 2017. In the Cloud explorer, you can drill down Subscription -> Resource Group -> App Service -> Files. Then, at the bottom of the Cloud Explorer, click "Download Files as a Zip."

Does VSTO run on Windows Azure?

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.

Resources