Recently we were getting the below pop up in Windows every time after restart.
The fix was to Disconnect the work / school account.
Navigate to Accounts è Access work or school
Click on Disconnect the work or school acount.
That fixed the issue for us.
Hope it helps..
With recent security enhancements in Customer engagement apps, the maximum user session timeout of 24 hours is removed.
Now it uses the Azure AD Session Policy to manage user session timeout, which by default has Azure AD refresh token expiration set as 90 days.
Refresh toke lifetime and expiration – https://docs.microsoft.com/en-us/azure/active-directory/develop/refresh-tokens#refresh-token-lifetime
Use Configuring sign-in frequency in Conditional Access to define the periods before a user is required to sign-in again – https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime
Earlier the default session timeout used to be 24 hours with 20 minutes for warning the user – https://nishantrana.me/2017/11/17/configure-session-timeout-and-inactivity-timeout-dynamics-365/
However, we can still override the default Azure AD Session policy, by setting the session timeout and/or inactivity timeout for the individual environment.
To set the same navigate to –
Environments > [Environment] > Settings > Privacy + Security in Power Platform Admin Center.
Specify appropriate values and save the changes.
Get all the details here –
Hope it helps..
Unified Routing can be configured in Customer Service Hub or Omnichannel Admin Center.
To configure it for Dynamics 365 Customer Service, navigate to
Service Management >> Service Configuration Settings >> Unified routing
(requires Tenant administrator’s consent – click on Provide Consent link)
Accept the permissions requested and provide the consent.
In case unified routing remains disabled –https://nishantrana.me/2022/03/08/solved-disabled-turn-on-unified-routing-option-in-dynamics-365-customer-service-hub/
Unified Routing once switched on, cannot be disabled from the application, and we need to contact Microsoft Support to turn it off.
The provisioning starts
After a couple of hours, we can see Unified Routing configured for the Customer Service app.
We can see the following solution – Anchor solution for UnifiedRoutingForCS in Dynamics 365 solutions installed in the environment.
Hope it helps..
Suppose we want to Test & Enable Mailbox of the below user programmatically.
We can see the below notification for the disabled mailbox.
This mailbox is disabled for email processing. For more information, see the alerts.
Below is the sample code –
On running the code, we can see the notification removed and the mailbox for the user enabled successfully.
C# Code –
CrmServiceClient svc = new CrmServiceClient(ConnectionString);
if (svc.IsReady)
{
var mailBox = new Entity("mailbox", new Guid("C88A539A-F493-EC11-B400-000D3A4F37D3"));
// testemailconfigurationscheduled = Indicates if the email configuration test has been scheduled for a mailbox record
mailBox.Attributes["testemailconfigurationscheduled"] = true;
svc.Update(mailBox);
Hope it helps..
Suppose we want to Approve the Email for the mailbox of the user(s) programmatically.
We’d see the below notification for the user whose mailbox is not yet approved.
Email won’t be processed for this mailbox until the email address of the mailbox is approved by an Office 365 Global Administrator or by an Exchange Administrator. For more information, contact your system administrator.
Below is the sample code –
On running the code, we can see the notification for the email address approval removed or the mailbox approved for the user.
C# Code –
CrmServiceClient svc = new CrmServiceClient(ConnectionString);
if (svc.IsReady)
{
var systemUser = new Entity("systemuser", new Guid("C48A539A-F493-EC11-B400-000D3A4F37D3"));
// emailrouteraccessapproval - status of the primary email address
//0 = Empty, 1 = Approved, 2 = Pending Approval, 3 = Rejected
systemUser.Attributes["emailrouteraccessapproval"] = new OptionSetValue(1);
svc.Update(systemUser)
The code should run under the context of the user who has either Global Admin or Exchange Admin role.
Hope it helps..
Nishant Rana's Weblog 