Dynamics 365 Customer Voice

Enable Managed Environments in Power platform

In this blog we will see how to enable managed environments in power platform.


  • User need one of the security roles assigned to them – Global Admin, Power Platform service admin, or Dynamics 365 admin Azure Active Directory role.
  • Users with the Delegated Admin role or the Environment Admin security role are not allowed to change the Managed Environments property in an environment.


Once enabled, there are 3 options as listed below,

  • Limit Sharing
  • Usage Insights
  • Data Policies

Please note – Once enabled, all users will need Power Apps or Power Automate licenses to continue using apps and flows in this environment.

  • Please click on Enable as shown in above picture.

We have successfully enabled the managed environments feature.

Dynamics 365 Customer Voice

Dynamics 365 Field Service with Remote Assistance

In this blog, I will describe easy steps on how to achieve Remote Assist Collaboration with Dynamics 365 Field Service module.


  • Dynamics 365 Field Service combines Internet of Things (IoT), mixed reality, computer vision, and intelligent automation features to help businesses automate remote fixes and troubleshooting.
  • Dynamics 365 Field Service combines with Dynamics 365 Remote Assist, a mixed reality-powered remote collaboration solution. When Remote Assist is paired with Microsoft HoloLens, it promotes higher first-fix rates by technicians. It does it by allowing HoloLens users to view work orders, call specific experts, and view information linked to works orders.


  • A Microsoft Azure tenant with a Dynamics 365 subscription.
  • Dynamics 365 Remote Assist subscription.
  • Admin access to add or update the Dynamics 365 tenant instance.
  • Dynamics 365 Field Service version 8.2 or later.(to include include the My Bookings for Today view.  With in the Dynamics 365 Subscription.
  • Android Device – The deep link from Field Service Mobile to the Remote Assist mobile app is currently available on Android only. Technicians using iOS devices must manually open Remote Assist mobile.
  • Two user accounts – one for the technician (front-line/support worker) and another for the remote collaborator.
  • The remote collaborator only needs a Microsoft Teams license.
  • The technician user will need a Dynamics 365 Field Service license, a Microsoft Teams license, and a Dynamics 365 Remote Assist license. (Note: A Remote Assist license includes Teams.)

Remote Assist Collaboration:

  • Dynamics 365 Field Service with Remote Assist Integration will allow support workers using Remote Assist on HoloLens to see their Field Service bookings and quickly call the remote collaborator listed in the booking’s Support Contact field.
  • By integrating Field Service and Remote Assist, we can:
    • Launch Remote Assist mobile directly from a Field Service Mobile booking via deep links.
    • See relevant work order information.
    • Post the Remote Assist call information to the associated work order’s timeline.

Connected Field Service with Remote Assist:

Device options and requirements for a Remote Assist user:

DeviceOS RequirementDetails
Remote Assist on mobile devicesDynamics 365 Remote Assist mobile is available on all devices, including Arora-enabled Android phones or tablets, ARKit-enabled iOS iPhones or iPads, and mobile devices without AR support.List of AR-supported devices on Android and iOS.   https://developers.google.com/ar/discover/supported-devices To access Remote Assist from devices that does not support AR   Steps: https://docs.microsoft.com/en-us/dynamics365/mixed-reality/remote-assist/mobile-app/using-devices-without-ar

Device options and requirements for a remote collaborator using Teams:

DeviceOS RequirementsDetails
Teams application on Windows 10 PCAny Windows 10 build.A Windows 10 PC running the Teams PC application can collaborate with Remote Assist on HoloLens, HoloLens 2, or qualifying Android or iOS mobile devices.   Reference: Links above
Teams application on mobile deviceAny iOS or Android phone or tablet running Teams.A phone or tablet running the Teams mobile application can collaborate with Remote Assist on HoloLens, HoloLens 2, or qualifying Android or iOS mobile devices. Reference: Links above

Network requirements:

• The recommended bandwidth for Remote Assist is at least 1.5 Mbps. When using Remote Assist on mobile devices in low-bandwidth environments, you can operate at bandwidth levels between 150 kbps and 1.5 Mbps. For more information. Reference: see the low bandwidth documentation.

• When using Remote Assist on mobile or HoloLens, any non-audio or non-video network-related activities may impact call quality. Examples include the Teams user sharing a file or the Remote Assist HoloLens user taking a snapshot that is automatically uploaded to OneDrive. After these non-audio or non-video network-related activities are completed, outgoing call quality may take up to 15 seconds to recover.
Note: Though audio and video calls might be possible in environments with reduced bandwidth, you might experience feature degradation, limiting the user experience.

Dynamics 365, Dynamics 365 Customer Voice

Add Custom Domain in Dynamics 365 Customer Voice Survey

  • Logon to portal.office.com
  • Navigate to Settings->Org Settings->Services->Dynamics 365 Customer Voice
  • Click on Add Domain ->Enter the Domain name and click on next
  • Make Sure you enter a valid domain name without any https:// or www:// prefix.
  • Click on next once entering the domain.
  • System displays CName, CName and TXT values. These values need to copied in DNS records of the domain.( NOTE: In my case domain is purchased from godaddy and I need to add the DNS records in GoDaddy site.
  • The name values entered in DNS Records in GoDaddy should not have the domain suffix for names. The value in DNS should be fpeurkey1_domainkey and fpeurkey2_domainkey instead of fpeurkey1_domainkey.devisdemo.com and fpeurkey2_domainkey.devisdemo.com
  • Once the values are added in DNS Records, in portal.office.com screen click on Verify.
  • The records will be verified successfully and we need to enter the email address in the custom domain.
DNS Records Name and Value
Verify Domain
  • Once the domain is successfully verified, add the Distribution members email address in the below screen. These email ids associated here should have a valid mailbox configured for their ids.
  • The Approved User should be a global admin or Customer Voice licensed User.
Review and click on finish
Distribution member added successfully
Dynamics 365 Customer Voice

About Me!

I am Devikumari Krishna, a Solution Architect with 15+ years of experience in various phases of software Development lifecycle. Proficient in analyzing and translating business requirements to technical requirements and architecture.

Being a Dynamics 365 and Power platform expert, I have experience in Sales, Customer Service, Field Service, Marketing, CRM Dynamic Portals, and CRM Integration with Azure, Power Automation Flow, and Data Verse.

In my Blog

  • I will target to give my learning and implementation experience as step by step instructions for others to follow.
  • I will make sure the information is crisp and useful for Dynamics 365 technologists.
  • I will target to cover Power Apps, Dynamics 365, Azure and Data Verse in my blog.