Office Web Apps Azure The Soldier of Fortune. Office Web Apps is an added value to every collaboration deployment, especially if you like to use Share. Collaborate for free with online versions of Microsoft Word, PowerPoint, Excel, and OneNote. Save documents, spreadsheets, and presentations online, in OneDrive. Point with business intelligence features. Dashboard on Excel rendered on browser, for example, gives your boss the most out of experience. Ive recently seen several cases of Office Web Apps deployment on Azure Iaa. S and even been engaged in investigation and troubleshooting. Licensing Problem. What is interesting to me is that all people who have asked me for help do not know about licensing model that Microsoft conducts for Office Web Apps on Azure Iaa. S. From the technical perspective, deploying Office Web Apps on Azure Iaa. S is similar to the one on your on premises environment. Unfortunately, from the licensing perspective, Office Web Apps is not supported to be used on Azure Iaa. S. Its like if you do not have a driving license you still can drive your car on the road, but if you are caught by a police and get asked your license, you will run into a big problem in terms of legality. To fully use Office Web Apps, you must be licensed Microsoft Office product which is not applied to license mobility program Microsoft offers for Azure Iaa. S. Trevor gave his thought on the right of Office Web Apps on Azure Iaa. Below you may find the build numbers, descriptions, KB article links and direct download links for all SharePoint Server 2013, SharePoint Foundation 2013. We continue our journey in configuring our SharePoint 2010 farm and today we shift our focus to one of the many exciting new inclusions in SharePoint 2010, Office. Microsofts range of Office Web Apps are finally getting realtime editing today. Word, PowerPoint, and Excel are all being updated with the ability to. Office Web Apps 2013 PatchesOffice Web Apps 2013 UpdatesS here Share. Point on Azure Why I wont recommend it. This post also gives you sort of full story of the license Office Web Apps in a hosted environment breaks your licensing agreement. At the end of the post there is a conclusion that Office Web Apps is still supported. This licensing agreement is also applied to Office Online Server. Anyway, its much better to talk to your license representative or directly to Microsoft licensing team. I asked a friend of mine working with Amazon AWS and got the link here regarding Office Online Server on Amazon AWSHybrid deployment for Office Web Apps I would assume running Office Web Apps on Azure Iaa. S is not allowed. So, what would be possible to deploy right now Whether you choose to deploy Office Web Apps on another Iaa. S provider or your own on premises environment, you still need pretty much to get into a hybrid deployment. In such a hybrid deployment, there is a site to site VPN which connects your on premises Office Web Apps to an Azure hosted domain controller in Azure network. The Azure VPN gateway model you choose depends on your allocated budget, scenario and security policy. Saying if you need to have a secured connection throughout IPSec tunnel, do have a look into Site to Site. Office Web Apps 2013 Sp2' title='Office Web Apps 2013 Sp2' />If you just need a pilot test of hybrid deployment, use Point to Site as this model does not require complex setup. More information, refer to Planning and Designing for Azure VPN Gateway and Connecting your on premises network to Azure. This diagram above illustrates simplest topology for a hybrid deployment. Office Web Apps machine WAC is joined to an Azure domain controller VM dont confuse with Azure AD which is a Paa. S Active Directory service. Your web application shall consume WOPI service to provide your end users Office Web Apps functionality. If your domain controller is hosted on the same on premises environment with your Office Web Apps machine but make sure these machines are different from each other, everything from Office Web Apps part should be fine. In the environment that requires security policy, you may need to submit outbound IP address if your custom web app is hosted on Azure App Service. You can find the list of outbound IP Address via Properties field in your web app. Refer to this article for more information Azure Web Apps Outgoing IP QuestionAnswer. Of course, technically Office Web Apps can be deployed and fully function on Azure Iaa. S. Finally, just a note that if you are going to propose Office Web Apps or Office Online Server to your customer, make sure you have a confirmation from Microsoft licensing representative. Updated December 2. PM GMT7 In the case of using Azure App Service, you are still able to achieve Office Web Apps functionality in your custom web app e. ASP. NET MVP by building a WOPI host to work with Office Web Apps WOPI service. Some references below help you get startedUpdate December 2. PM GMT 7 Update link to getting outbound IP address for Azure App service hosted custom web app in case your organization needs to configure network based firewall. Enable Office Web Apps working in both Internal and External environment The Soldier of Fortune. Share. Point folks did complain the poor performance of their Share. Point machines in the past at the time when Office Web Apps was tightly integrated in Share. PYB03qlJ-Dg/UUILW3-pdJI/AAAAAAAABS0/o5DYbxtVzf0/s1600/owa+download.png' alt='Office Web Apps 2013 Configuration' title='Office Web Apps 2013 Configuration' />Point Server 2. Office Web Apps services must be started in every Share. Point machine for end user to be able to view and edit supported Microsoft Office products Word, Excel, Power. Point, One. Note directly on their browser. Thankfully with the new release of Microsoft Office system, Office Web Apps is no longer integrated in Share. Point 2. 01. 0. Its now a separate commercial product and cant be installed in any server where Share. Point Server 2. 01. This significant change allows you to only have a server that is able to function to any Share. Fate Stay Night Visual Novel English Psp here. Point farm that connects to the OWA server. This improves performance a lot. The burden to your organization is that you have to prepare either a dedicated machine for OWA or install it on a non Share. Point machine and purchase its license. This surely costs pretty much money for both hardware and licensing. Im not going to go around the pros and cons of OWA Server 2. To see more about the enhancement and new changes, read here. One of the very common questions Ive seen in the MSDN forum is the setup of OWA working in both internal and external environment. This thread has inspired me to write my note in this article to answer to the question. Below is the word for word question I have successfully installed Share. Point 2. 01. 3 and Office Web Apps on Azure VMs inside an Azure Virtual Network Iaa. S model. Everything is working well. However, my testing has shown that external users and internal users cant use Office Web Apps at the same time. Office Web Apps, installed on its own vm, accommodates an external and internal URL quite well. However, Share. Point 2. WOPI Zone, either internal or external but not both. Ive set the WOPI zone to Internal HTTPs Set SPWOPIZone Zone internal https. OWA works just fine if accessed from inside the Azure Virtual Network. However, if I try to access from outside the Virtual Network, from the Internet, Office Web Apps fails. The exact opposite is also true. I can set WOPI Zone to External HTTPS and accessing from the Internet works fine, but accessing inside the Virtual Network fails. In this case, lets say you have completely deployed and configured OWA in your internal environment. End users from local network have access to Share. Point through the internal URL e. Internet Explorer. However if end users access Share. Point from Internet using the Internet published domain e. OWA doesnt work because it from Internet routes to the internal URL you have set e. This happens many times when you dont setup WOPI zone correctly. In my environment, there are two machines app. The app. 03 machine has Share. Point Server 2. 01. Office Web Apps Server 2. These have already been joined to the domain controller with the name availys. Note that all of these machines are hosted in my developmenttesting environment. Your environment may be different from mine. The Share. Point farm is virtualized inside Hyper V and each machines has been assigned an internet public IP. On the Share. Point machine, if you havent configured Alternate Access Mapping setting yet, open it in your Central Administration site. Application Management Configure alternate access mappings. In my case, the name of the web application Ive created is http app. Now I need to edit its public URL to make it accessible from the Internet using my public URL http ecodemo. To tell you my guidance is actually correct, I have to be using the real domain name and the current configuration of the Share. Point farm in this article. On the Alternate Access Mappings page, click Edit Public URLs then select web application at Alternate Access Mapping Collection setting. Under the Internet setting, enter your public URL. You then dont necessarily have to edit binding setting in IIS if you arent using multiple addresses running in the same port. After that, check the internal URL from local network while opening the public URL from the Internet. Make sure you have done configuring your Internet domain name to point to the public IP of the Share. Point machine. This can be done via domain control panel and depends on what hosting provider you are using, such as Go. Daddy. In my case, Im able to access http app. Internet as below. Now open OWA machine to create a new WAC farm. New Office. Web. Apps. Farm Internal. Url http app. External. Url http 1. Editing. Enabled. Because Ive not configured my OWA machine to be published to the Internet so I have to use its Internet public IP. Its not a recommended best practice. In your case, the external URL would be http owa. Above Im not using SSL certificate to encrypt data over the Internet. Just add Certificate. Name parameter if you want to use whether CA issued certificate or self signed certificate. Finally, check both internal URL http app. URL http 1. 98. Your screen should display XML structure. Now you need to re bind all Share. Point machines to WAC farm using New SPWOPIBinding http technet. Next, you just need to set the WOPI zone for external use even there is an internal use in your Share. Point environment. Set SPWOPIZone zone external http. Finally, configure Excel service and then upload an Excel workbook into a document library and check it. Below are the screenshots of OWA working on both internal and external environment. As you see, there is no cheat that we used to use when playing game in childhood. The key thing here to note is that the FQDN of my Share. Point server isnt published to the Internet because the domain controller and DNS is configured and run locally. Only Internet domain points to the public IP of the Share. Point machine. This would be the flickering light you would need to consider for Share. Point publishing portal. The lesson learnt here is not to use the real name of domain controller if you plan to use it over the Internet. For example, the FQDN domain controller shouldnt be named abc. Ideally it should be something like abc. Microsoft wrote an article about naming conventions in Active Directory. If you are using Windows Azure Iaa. S service to build and host Share. Point virtual machines, there are many required steps before deploying Office Web Apps. First, you need to create a virtual network to make your virtual machines possible to communicate with each other in the local network. Second, create endpoint with TCP protocol in conjunction with port 8. Share. Point machine to be able to communicate with others over the Internet. Below are some references that could help Working with network stuffs in Windows Azure looks like a night mare no ITPros  want to see in their dream. In real world scenarios, your environment may have firewall or reverse proxy Forefront TMG, UAG, F5, Astaro. OWA server should be published through firewall for better secure. This is always a good recommendation.