Menu Close

Blog

Slide 1
UK365GUY

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Subscribe
Slide 2
UK365GUY

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Subscribe
Slide 3
UK365GUY

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Subscribe
previous arrow
next arrow

{Do you know} Recover deleted records from recycle bin on Dataverse

uk365guy

Hello Everyone,

Today I am going to share my thoughts on the Recovering the deleted records from recycle bin on Dataverse.

Let’s get’s started.

Usually Deleted records are not recoverable on Dataverse, but with the introduction of new feature Recycle Bin(Preview) you can restore deleted records.

Now Admin can view and recover any deleted records within a configurable time period up to 30 days.

How do you enable on Power Platform Admin Center?

Login into www.admin.powerplatform.microsoft.com

Go to the environment > Settings > Features >

If disabled, admins will not be able to view or recover any deleted records. Disabling this feature could take up to 10 minutes.

Note: Configure recovery time interval(up to 30 days).

That’s it for today.

I hope this helps

Malla Reddy Gurram(@UK365GUY)
#365blogpostsin365days

Share this:

{Do you know} Prevent data exfiltration with user level controls on Dynamics 365 Model Driven Apps

uk365guy

Hello Everyone,

Today I am going to share my thoughts on Prevent data exfiltration with user level controls on Dynamics 365 Model Driven Apps.

Let’s get’s started.

To prevent data exfiltration with user level controls, you can implement several strategies. Here are some key points to consider.

Granular Control Through Security Roles: Assign security role to users, allowing only those with approved roles to run pre-authorized apps in the environment.

Audit Mode: Enable an audit mode to review all app accesses and download audit logs for analysis.

Conditional Access: Set conditional access policies to control which users can run authorized apps.

By default when this feature is activated, only approved Microsoft solution apps can run in an environment, such as Dynamics 365 Sales or Dynamics 365 Customer Service. The local environment admin sets what apps can run by their authorized users in an environment.

Unauthorized apps are blocked when the user tries to access the environment. To help administration with selecting which apps to approve for their environment, an audit mode run can be enabled.

This is where all apps accesses are audited and the admin can download this audit log for review.

Conditional access on which users can run what authorized apps can be set by the administrator.

The administrator can allow list an app for selected security roles. Only users who have the selected security roles can run the app in the environment.

That’s it for today.

I hope this helps
Malla Reddy Gurram(@UK365GUY)
#365blogpostsin365days

Share this:

{Do you know} Maintain security role privileges for better ALM solution import on Dataverse

uk365guy

Hello Everyone,

Today I am going to share my thoughts on the maintain security role privileges for better ALM solution import on Dataverse.

Let’s get’s started.

Let’s discuss maintaining security role previleges for better Application Lifecycle Management(ALM)
solution imports. When working with Power Platform and Dataverse managed solutions, it’s essential to handle security roles effectively.

Here are some key points:

1. Feature details:

When a Power Platform admin modifies security roles that are system predefined customizable or custom security role previously imported by a Dataverse managed solution, these customizations can be overwritten by importing an update to the managed solution containing those security roles or when the system refreshes these security roles.

With the new feature, the system will merge the predefined customizable security roles. custom security roles, and privileges with the updates made by the Power Platform admin in an environment. This way, preexisting updates won’t be overwritten.

2. Use Cases:

Application Lifecycle Management(ALM): This feature supports the ALM process by ensuring that security role privileges updates are honored after managed solution imports.

Custom Security Role: You can now allow custom security roles to be updated in partner-managed solutions.

Better Control: By merging security role changes, you have better control over the security model during solution imports.

3. Alternative Approaches:

Account Management: Consider using accounts managed by an admin or deployer team to import solutions.

ALM Integration: Explore ALM integration with GitHub actions or Power Platform Pipelines, where impersonated accounts handle solution imports.

Remember that the specific approach may vary based on your organization’s requirements and the type of solutions you’re working with. Always test thoroughly before implementing changes in a production environment.

That’s it for today.

I hope this helps

Malla Reddy Gurram(@UK365GUY)
#365blogpostsin365days

Share this:

{Do you know} Assisted mapping for standard dataflows in Microsoft Dataverse

uk365guy

Hello Everyone,

Today I am going to share my thoughts on the Assisted mapping for standard dataflows in Microsoft Dataverse.

Let’s get’s started.

Suppose there is a data migration work where you need to map the fields for the table selected manually which is daunting task isn’t it?

So with the introduction of the assisted mapping for standard dataflows you will be assisted with mappings.

Assisted mapping for standard dataflows in Microsoft Dataverse is a powerful feature that simplifies the integration of external data into existing Dataverse tables.

Let me break it down for you:

1. AI-Assisted Mapping: This feature leverages artifical intelligence to recommend column mappings when bringing data into Dataverse tables. It increases productivity by speeding up the mapping process and providing confidence in the results. When loading data, you map the source query’s columns in the dataflow’s editing experience to the destination Dataverse table columns.

2. Recommendations and Mismatches: The AI suggests existing Dataverse tables that the new data should be mapped to. After choosing a target Dataverse table, it advises how the columns should be mapped and notifies users of any column type mismatches that need to be addressed before completing the dataflow.

3. Enhanced Data Migration: Assisted mapping ensures a faster and smoother data migration experience by bypassing business logic. It also consolidates the experience for loading data from Excel directly into a Dataverse table or integrating Fabric One Lake as a data source with a no ETL no copy apptoach.

4. Security and Collaboration: Dataverse provides integrated experience to upgrade from export to data lake, maintains security role privileges for better ALM (Application Lifecycle Management) solution imports, and allows for masking sensitive data with column level security.

Additionally security features prevent data exfiltration, scan files and attachments for viruses and malware and focus on collaboration and accessibilty.

In summary, assisted mapping simplifies the mapping process, enhances data migration, and ensures robust data management within Microsoft Dataverse.

That’s it for today.

I hope this helps

Malla Reddy Gurram(@UK365GUY

#365blogpostsin365days

Share this:

{Do you know} Implement Anywhere365 Solution for Omnichannel features on Microsoft Dynamics 365 Customer Service and Microsoft Teams

uk365guy

Hello Everyone,

Today I am going to share my experience on the Anywhere365 Solution which is useful for Omnichannel Feature implementation on Dynamics 365 Customer Service and Microsoft Teams.

Let’s get’s started.

Suppose there is a requirement to implement a solution where the call center users should receive calls on their Microsoft Teams and BE shown the customer information from Dynamics 365 Customer Service if the Calling customer information exists on your Dynamics 365 Customer Service.

As i have evaluated a solution for one of our customer:

Solution: Anywhere365: https://anywhere365.io/platform/solutions/microsoft-teams-contact-center

Requirement to implement Anywhere365:

1. Dynamics 365 Customer Service

2. Microsoft Teams Integrated with Dynamics 365 Customer Service.

3. Microsoft Teams Phone Number.

4. Assign the Anywhere365 License.

5. Configure the Workstream on your Dynamics 365 Customer Service.

Installation on Dynamics 365 Customer Service:

https://golive.anywhere365.io/platform_elements/webagent_for_dynamics365/webagent_configure_for_dynamics_cif2.html

WebAgent for Dynamics 365 User Guide:

https://golive.anywhere365.io/platform_elements/webagent_for_dynamics365/webagent_for_dynamics365_userguide.html

Attendant Console for Teams Installation

https://golive.anywhere365.io/platform_elements/attendant-console/attendant-console-for-teams/attendant-console-teams-configuration.html

Configure Teams Auto Attendant using Teams Admin Center:

https://golive.anywhere365.io/platform_elements/attendant-console/attendant-console-for-teams/configure-auto-attendant-teams-admin-center.htm

That’s it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365blogpostsin365days

Share this: