Office 365: FAQs about Flow y PowerApps (II)!

As a continuation of the previous article about Flow and PowerApps FAQs, this time I’m sharing a new article with additional FAQs about both Office 365 services:

Q. How can restrict my users’ ability to move data out of corporate certified environments like SQL and SharePoint to insecure, legacy or consumer technologies?

A. PowerApps and Flow allow you to create data zones for business and non-business data, as shown below.  Once these DLP policies are implemented, users are prevented from designing or running PowerApps and Flows that combine business and non-business data.   For more details, see https://flow.microsoft.com/en-us/blog/introducing-data-loss-prevention

PAFPolicy.PNG 

Q. How can Office 365 customers connect to custom data sources?
A. Every Office 365-licensed user of PowerApps and Microsoft Flow can create a custom API data connection, in addition to the intrinsic ability to connect to sources like SQL, Exchange, Yammer, Box and Twitter.

Q. How can I prevent new users from starting to use PowerApps until the organization is ready?

A. We have extensive documentation on this topic at https://powerapps.microsoft.com/en-us/tutorials/signup-question-and-answer The short answer is to use the PowerShell cmdlet:

Set-MsolCompanySettings -AllowAdHocSubscriptions $false

which prevents users from activating “ad-hoc” service like PowerApps, Power BI or Azure RMS.

Q. How can I remove PowerApps and/or Flow from existing users?

A. Again, see https://powerapps.microsoft.com/en-us/tutorials/signup-question-and-answer for a comprehensive overview.  The quick answer is to use the Office 365 Admin center and remove the license for PowerApps and Flow.  Also, the integrated list button to create PowerApps and Flow require design permissions on the list. Users, even if licensed, will not see those buttons on any list or library where they don’t already have design rights.

Also, inside the Office 365 SharePoint license (e.g. Office 365 E3) disable access to the PowerApps and Flow services as shown:
ServiceLicenseRestriction.PNG 
This will remove the PowerApps, Flow, and Dynamics 365 icons from the AppLauncher “waffle”.

Bulk removal of licenses is also possible through PowerShell. See https://technet.microsoft.com/en-us/library/dn771774.aspx for a detailed example.   Finally, further guidance about bulk removal of services within a license can be found at https://technet.microsoft.com/en-us/library/dn771769.aspx

Office 365: FAQs sobre Flow y PowerApps (II)!

Siguiendo con la serie de artículos sobre FAQs de Flow y PowerApps, os comparto una serie de cuestiones típicas adicionales que se han publicado en la Microsoft Tech Community.

Q. How can restrict my users’ ability to move data out of corporate certified environments like SQL and SharePoint to insecure, legacy or consumer technologies?

A. PowerApps and Flow allow you to create data zones for business and non-business data, as shown below.  Once these DLP policies are implemented, users are prevented from designing or running PowerApps and Flows that combine business and non-business data.   For more details, see https://flow.microsoft.com/en-us/blog/introducing-data-loss-prevention

PAFPolicy.PNG 

Q. How can Office 365 customers connect to custom data sources?
A. Every Office 365-licensed user of PowerApps and Microsoft Flow can create a custom API data connection, in addition to the intrinsic ability to connect to sources like SQL, Exchange, Yammer, Box and Twitter.

Q. How can I prevent new users from starting to use PowerApps until the organization is ready?

A. We have extensive documentation on this topic at https://powerapps.microsoft.com/en-us/tutorials/signup-question-and-answer The short answer is to use the PowerShell cmdlet:

Set-MsolCompanySettings -AllowAdHocSubscriptions $false

which prevents users from activating “ad-hoc” service like PowerApps, Power BI or Azure RMS.

Q. How can I remove PowerApps and/or Flow from existing users?

A. Again, see https://powerapps.microsoft.com/en-us/tutorials/signup-question-and-answer for a comprehensive overview.  The quick answer is to use the Office 365 Admin center and remove the license for PowerApps and Flow.  Also, the integrated list button to create PowerApps and Flow require design permissions on the list. Users, even if licensed, will not see those buttons on any list or library where they don’t already have design rights.

Also, inside the Office 365 SharePoint license (e.g. Office 365 E3) disable access to the PowerApps and Flow services as shown:

ServiceLicenseRestriction.PNG 
This will remove the PowerApps, Flow, and Dynamics 365 icons from the AppLauncher “waffle”.

Bulk removal of licenses is also possible through PowerShell. See https://technet.microsoft.com/en-us/library/dn771774.aspx for a detailed example.   Finally, further guidance about bulk removal of services within a license can be found at https://technet.microsoft.com/en-us/library/dn771769.aspx

[Events]: SPS Madrid 2017 is being cooked and it will take place on the 20th of May, 2017!

The SPS Madrid organization team is thrilled to announce that 2017 edition will take place on the 20th of May at Microsoft Iberica headquarters. We will be publishing all the news about the event at the SPS Madrid web site, so stay tuned. We are also glad to announce you that SPS Madrid 2017 call for sponsors is now open, so if you are interested in become one of our wonderful sponsors, please hurry up and book your spot as soon as possible J.

http://www.spsevents.org/city/Madrid/Madrid2017/home

image

[Eventos]: Ya tenemos fecha para el próximo SPS Madrid: 20 de mayo de 2017!

Desde el equipo organizador del próximo SharePoint Saturday (SPS) Madrid nos complace anunciaros que la fecha elegida es la del 20 de mayo de 2017 y el lugar las oficinas de Microsoft Ibérica en Madrid. Estad atentos al sitio del evento en el que iremos publicando todas las novedades del evento. Para empezar, nos complace anunciaros que el call for sponsors ya está abierto, por lo que si estáis interesado en patrocinar el SPS Madrid, es importante que reserves lo antes posible tu participación.

http://www.spsevents.org/city/Madrid/Madrid2017/home

image

Office 365: New Admin Center Previe for ODBF!

Microsoft have just released some days ago the preview of the New Admin Center for ODFB. This preview Admin Center, which is available at https://admin.onedrive.com/, is composed by the following elements (Source: Stephen Rose’s post at Microsoft Tech Community):

  • Home section: This is the dashboard for the admin center and will soon show recent Office 365 Message Center posts and usage reporting related to OneDrive for Business.

image

  • Sharing: This section helps admins gain control over how and with whom your users are sharing information. This includes controlling the use of external sharing and anonymous links, as well as limiting which external domains users can share with.

image

    • Sync: Admins can block syncing of specific file types and deny syncing to non-domain joined PCs.

image

    • Storage: This section allows admins to easily set default storage limits and document retention durations.

image

    • Device Access: This gives admins control over how and from where a user can access their files. This includes allow/deny access from personal devices or specific networks as well as rich Mobile Application Management Intune policies for iOS and Android.

image

  • Compliance: Admins can find quick links to the Office 365 Security and Compliance Center for key scenarios like auditing, data loss prevention, retention, and eDiscovery.

image

Referencia:

Office 365: Preview del nuevo Admin Center para ODFB (I)!

Desde hace unos días  ya tenemos disponible la preview del nuevo centro de administración para OneDrive for Business (ODFB) al que podréis acceder desde la Url https://admin.onedrive.com/. El nuevo Admin Center para ODFB se compone de:

  • Una página principal con un dashboard que recoge mensajes del centro de mensajes de Office 365 e informes de uso relativos a ODFB.

image

  • Una sección “Sharing” que permite al administrador visualizar como y con quien se comparte información. Desde esta sección se puede configurar si es posible compartir de forma externa, el uso de enlaces anónimos o los dominios externos con los que se puede compartir.

image

  • Una sección “Sync” desde la que se puede bloquear la sincronización de tipos de archivo concretos o denegar la sincronización a equipos no unidos al domino.

image

  • Una sección “Storage” que permite al administrador definir tanto el espacio de almacenamiento de ODFB disponible como el número de días que la información se retiene desde que se borra una cuenta de usuario.

image

  • Una sección Device Access que permite a los administradores controlar como y desde que dispositivo se accede a la información. Se incluye permitir / denegar el acceso a ODFB desde dispositivos personales o redes concretas, así como políticas de Intune para MAM (Mobile Application Management) en el caso de dispositivos iOS y Android.

image

  • Finalmente la sección Compliance facilita el acceso a las funcionalidades y capacidades del Compliance & Security Center en escenarios clave de auditoria, DLP, retención and eDiscovery

image

Referencia: