User Profile
Nithyanandham_S
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
IVR configuration in Microsoft teams - Configure Busy call message
Hi All, Please share your thoughts. I am currently working on Microsoft Teams IVR configuration for one of our customers. In my setup, I have a main Auto Attendant that transfers calls to either an English-speaking or Arabic-speaking Auto Attendant. Based on the menu selections, calls are then routed to an operator. Additionally, both Auto Attendants are configured with a "Dial by Extension" feature, allowing users to reach specific extensions directly. My question is regarding the busy message configuration. I have noticed that the Auto Attendant transfers a second call to a user's extension even when the user is already on an active call. Is there a configuration available to play a busy message, such as "The user is currently on another call. Please try again later"?288Views0likes2CommentsJournal rule duplicate external mails when office 365 tenant is onboarded with Exclaimer cloud
Hi All, Journal rule in office 365 is duplicating only mails to sent to external domains after office 365 tenant is onboarded with Exclaimer cloud Exclaimer signature stamping process for office 365 users is given below : Step 1 - When any user in office 365 tenant sent a mail, the mail will first reach exclaimer cloud through send connector created in office 365 tenant. Step 2 - Then exclaimer cloud will receive the mail and do the signature stamping, then sent that mail back to office 365 tenant. Step 3 - We have the receive connector in office 365 which receives the mail from exclaimer cloud, then office 365 will deliver the mail to the appropriate recipient. We have journal rule in office 365 tenant, which will sent a copy of mails sent and receive by office 365 users to the journal mailbox located in Exchange On premise, the problem here is, the journal rule is acting twice in the above process only against the mails sent by office 365 users to external domains (for example http://gmail.com/) i.e journal rule is applying before the mail sent to exclaimer cloud and applying again after we receive mail from exclaimer cloud, as a result we are ending up with duplicate copy of the same mails in the journal mailbox. Let me know how we inform Exchange online not to trigger the journal agent again in the same mail ? or is there a way to avoid the delivery of duplicate copy of same mail to journal mailbox located in Exchange On premise ?1.1KViews0likes0CommentsChange User Sign In method from Password hash Synchronization to ADFS Authentication
Hi All, We have a requirement, users in the environment is currently using the primary Authentication method as Password hash synchronization, which has to be changed to ADFS authentication. In the current environment we have existing ADFS infrastructure in place, We wanted to have the federation between on premises active directory and Azure AD, then we want the users primary authentication method to be changed from Password hash synchronization to ADFS authentication. In addition, there are multiple custom domains added as verified domains in Azure AD, which are currently set as with the domain type as "Managed" Below is the plan we have Created to change the Authentication Mechanism 1. Convert all the domains type from Managed to federated using the commands Convert-MsolDomainToFederated -DomainName abc.com -SupportMultipleDomain Followed by the above command, We will execute the below commands for all other domains. Convert-MsolDomainToFederated -DomainName xyz.com Convert-MsolDomainToFederated -DomainName test.com 2. Then change the user sign in method present in Azure AD connect server from Password hash synchronization to Federation with ADFS We would like to clarify the following queries Is there a way to go with the staged approach, Say for example, change any single domain at a time from Managed to Federated, then change user sign in on the Azure AD connect server from Password hash synchronization to Federation ? If your answer is yes, the other managed domains would continue to use Password Hash synchronization as the primary authentication method ? What would be the end user experience and Impact , when we convert the domain type from managed to federated and set the primary authentication method as ADFS ? Should users need to sign out and sign in back to office 365 services ? What would be the default time taken configured by Microsoft to switch all the users authentication completely from PHS to ADFS authentication ? Any other important considerations which is not captured and that has to be taken care for this activity ? Appreciate your view and inputs on this query.Custom Azure SSPR URL for Password reset and Account Unlock
Hi All, We are testing SSPR and Combined registration in our environment. I wanted to use friendly name for the SSPR URL with my custom domain name for Password reset and Account unlock. Say for example I want my users to use the friendly name https://passwordreset.nithya.com and then I want the connection to be redirected to https://passwordreset.microsoftonline.com/ or https://passwordreset.microsoftonline.com/?whr=nithya.com Kindly help me with your insights.
Recent Blog Articles
No content to show