A certificate that has a private key requires user profile and, by default, an Azure WebApp doesn’t create the user profile. This displays just below usage grid on the “Dashboard” panel of the web site.
In this instance, because some of the above tweaks didn’t make a major difference for Office 2013 (results with Office 2010 could vary), Office 2010 was re-installed due to growing pressure from the user base, and the virtual desktop performance was much improved.Since you already use App Insights, you can take snapshots of your application code / running processes, the following official guide is one approach: Enable Snapshot Debugger for. Note: The above certainly isn’t a comprehensive list of all tips\tweaks to cure to all issues! However, it’s a good ’round up’ from my research, whether some of the above are effective or not, it’s a case of picking out the tweaks which best suit the environment and test, test, test and measure the results!
Office Pro 2013 on Terminal Server, slows server down Microsoft Office 2013 needs 20 percent more capacity to maintain VDI performance However, I thought it would be useful for others, as I searched Google extensively for ‘microsoft office vdi performance’ Whilst investigating and searching for a solution, I came across many articles with tweaks\tips which I put together in a quick Word document. Platform: vSphere 5.1 and Horizon View 5.2 Note: Microsoft Office 2013 had been deployed in the parent image. The virtual desktop just became unresponsive. To keep it short and sweet, Microsoft Office (Outlook and Word), were monopolizing the CPU. A couple of months back, during a recent engagement, I was trouble-shooting end user performance problems.