Skip to main content

PowerApps and Flow released

Microsoft Flow and Microsoft PowerApps have finally been released to the public after beeing in preview for some time now (some might remember PowerApps as Project Siena).

Try it out and discover the easy business value these new services provide:


You have a new place to discover and run business apps.

Find and run all your business apps from a single place—Dynamics 365.

Publish apps with PowerApps to make them instantly discoverable in your org’s dedicated AppSource gallery.

Environments provide a space to store, manage, and share.

Create dedicated development, testing, and production environments.

Use environments to separate apps and data by geography or team.

Get enterprise-level management and security controls.

The Microsoft Common Data Service offers powerful app-building capabilities.

Model data using a set of standard entities with schemas that support common business themes.

Manage access to data down to the entity level using roles and permissions.


Manage your organization’s flows with enterprise-grade control using environments.

Use Environments to store your flows by geography or team.

Establish data-loss prevention policies to control the flow of data and the use of services within your organization.

Microsoft Flow offers more connectivity than ever—to Microsoft and third-party services.

Connect to 15 new services, including Basecamp 3, Bitly, Cognitive Services Text Analytics, Instapaper, and Pinterest.

Use Premium services like Salesforce and the Microsoft Common Data Service, which are exclusive to paid Microsoft Flow plans.


Popular posts from this blog

Install DLL in GAC - Windows 2008/2012 (Using Powershell, No GacUtil.exe)

If you want to install a DLL in the GAC and do not have the GACUtil.exe available. Powershell is properly the easiest way to procede.

Before Powershell you would properly just drag the DLL file into the C:\Windows\Assembly but this option is usually not available anymore.

Powershell - Add DLL to GAC So to install a DLL file in the GAC simply execute the below Powershell script. Remember you migth want to run the Powershell prompt as an administrator.
[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")$publish=New-ObjectSystem.EnterpriseServices.Internal.Publish$publish.GacInstall("c:\temp\MyDllFile.dll")iisreset
The first line adds a reference to the assembly we need to be able to mange the GAC.
The second and third lines retrives the GAC object and publish a new DLL file to it.
The last line resets the Internet Information Services. This is only needed if your DLL file is used in a websi…

SharePoint/Project Server - Firewall port open list

Firewall port open list Every time I have to install a new instance of Project Server I forget which ports have to be open.
The ports are divided into 3 lists, one list for the web front end servers, one list for the application server and one list for the SQL server.
These ports are based on a 2013 installation of SharePoint/Project Server. the 2010 installation defer a little bit.

Web Frontend ServerWhen a range is specified all ports between the range must be opened.
-80 TCPInhttp
-443 TCPInhttps/ssl
-25 TCPInSMTP for e-mail integration
-16500-16519TCPInPorts used by the search index component
-22233-22236TCPIn/OutPorts required for the AppFabric Caching Service
-32843-32845TCPInCommunication between Web servers and service applications
-32846TCPIn/OutSharePoint User Code Service
-808-809TCPInOffice Web Apps

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.

My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site