Unified Communication Techies

Teams SBA registration was showing different errors due to couple reasons and this article share the experience i went through on that.  This is the 3rd error Classic mistake i did was coping the Secret ID provided below because in Microsoft article says Application (Client ID) and Client secret.  I copied the Secret ID (which is wrong) instead of that it should be  Value should be copied and thats the client secret. Following is from Azure App registration.  Thanks to Nathan, he had a chance to work on App registration for another product prior and he was showing the mistake. This was the 1st issue which i faced, during that time i created the secret ID and App ID which i was used in wrong way but the error message i got was nothing to do with it. My expectation was is secret is wrong then Auth failure in seconds. This was the 2nd issue, This came when i try to do it on the SBA by providing Azure Application credential (being global administrator will do)  One ...

Now tenant admin can help with user for custom greetings,  DefaultGreetingPromptOverwrite and  DefaultOofGreetingPromptOverwrite many other user settings on behalf of users. This may help to end users when they are away to set up forwarding rules to another colleague or external number etc. Set-CsUserCallingSettings  -Identity "madushka@abc.com"  -IsForwardingEnabled $True -ForwardingType Immediate -ForwardingTarget taniya@abc.com -ForwardingTargetType SingleTarget - Verbose Note : You must have PhoneSystem License attached for you to have this forwarding to a another person. Basically both users must have PhoneSystem License.  Forward to external number   when you try this make sure you are using E.164 standard for phone numbers.  Set-CsUserCallingSettings -Identity " madushka@abc.com"   -IsForwardingEnabled $True -ForwardingType Simultaneous -ForwardingTargetType SingleTarget -ForwardingTarget "+1365888xxx"  - Verbose Note : You...

Hosting Provider  To share the same SIP address in On-prem and online (Teams) required hybrid to set/change Hosting Provider.  for you to run get-cshostingProvider you will required Skype for business Online (old) module or Skype for business ISO mount and install the tools. Hosting provider identity should be Office365  Proxy FQDN should be "sipfed.online.lync.com" Enable to $True Enabled Shared Address Space $True Host OCSUsers    $True VerificationLevel    $True AutoDiscoverUrl  need to set  https://webdir.online.lync.com/Autodiscover/AutodiscoverService.svc/root   Tenant Federation Configuration  SharedSIPAddressSpace should be True   Access Edge Configuration  Make sure set all the important properties you need to True  Check default configuration in this article -  Manage Access Edge Configuration for your organization - Skype for Business Server 2015 | Microsoft Docs

  I had a scenario where porting is completing and customer end devices are not ready/late delivery to the location. Had many user numbers and many reception numbers, which i didn't port everything but partial porting and this is one of the number +1 365 xxx 421 and since it is "ServiceNumber" from Local telco.  Due to the device not availability delay i have to look for an option asap. Option #1 - Convert this number to user number and add forwarder to reception number. it can be Teams client or may be number forwarded. Option #2 - Do the option#1 part of it and forward immediate Voicemail but for how many days? This wont be an option :D   Option #3 - Create new Auto Attendant immediately and Add the greeting (just like other reception number) so no one feel a difference or changes. Then all the call forwarded to existing to reception number: +1 365 xxx 6226 (Not migrated reception/main line) Best option will be Option #3 and i have created AA and ...

For virtual SBC to be connected with the M365 Tenant and this will be done via Azure App Registration -  Direct Routing SBA - Microsoft Teams | Microsoft Docs above article shows given the requirement but thought it will be better if someone write about the steps  It has 4 major steps (Not really major :) ) 1.  Register the application 2. Set the implicit grant tokens 3. Set the API permissions  4. Create the client secret However, for above steps even to start you will required the Azure Tenant Permission after you create the vSBC on it.  Following screen you will receive if permission is not available when you try to create an app on Azure AD Permission require: for this question to answer wont be able to find it on above Direct Routing SBA article and it will be mention on this -  Quickstart: Register an app in the Microsoft identity platform - Microsoft Entra | Microsoft Docs Once you have above permission/one of the permission  Cloud Application/A...

M365 Secure score - Turn on the common attachments filter setting for Anti-malware on EOP This filter will help us to prevent certain types of files that are risker to send and receive via e mails. To make sur e these file types don't get through, enable the common attachment filter.   How to acces s -    https://security.microsoft.com/ then go to Policies & Rules > Threat policies > Anti-Malware It will have a long list  You can use the default list of file types or customize it.  Messages with the specified attachments types are treated as malware and are automatically quarantined.  Change notification status to different organization requirement. 

DNS Suffix , Internal DNS zones, External DNS (M365_UCTechiLab#5) - AD and Exchange 2016 Access the AD Server and DNS and Create new DNS Zone.  I would suggest to fix the it/DNS suffix add then you can verify by accessing the ADUC and create user  For DNS work in the Exchange and also AADConnect to verify UPNSuffix we should have domain in the both side of the ADs. AAD will have the automatically when we verify part of the tenant verification by adding a CNAME in public domain where you have domain records. Addition to that if you dont have this in AD DNS (On-Prem) then you will required to add.  Follow the steps and it will be straight forward in new environment and if you already using this domain in your exchange then this wont be a problem or not required to create.  Go to Active Directory Server (AD) > AD Domains and Trusts     Right click on top Active Directory Domains and Trust > UPN Suffixes and Add the UPN you required  Once you sa...