Tuesday, August 6, 2019

Change the default email address and anonymous user to send email to Public Folder

An Exchange public folder can be used by several people in Outlook Web App or in their local Outlook installations. It allows a group of users to view and send e-mails from a common mailbox. These users can also share a common calendar.

Changing the default reply email address for Public Folder: For Public Folders you created, by default the email the address will be with initial domain (onmicrosoft.com).

  1. Go to EAC > Public Folders > Public Folder. 
  2. Select the Public Folder you created, check whether it is mail-enabled (If it is mail-enable, then only you can see the additional settings and email address is assigned).
  3. Click Edit.

  4. The address you can see for Public Folder (Twitter) is twitter@cloudcfs1.onmicrosoft.com. However, you can add SMTP over here, but that will not be your default reply address.
  5. Connect to Exchange Online through PowerShell.
  6. Once you are connected, you will need to disable the Email Address policy. Enter command “Set-MailPublicFolder -Identity "\<foldername>" -EmailAddressPolicyEnabled $False” (Provide you public folder name in place of <foldername>.



     
  7. After disabling Email Address Policy, you will see that "Make this the reply address" option will appear and hence you can enter the new SMTP address and make this as a default reply address.





Allow anonymous users to send email to a mail-enables public folder: Any emails sent from an anonymous user to the Public Folder you created, will bounce back if this permission is not given.
  1. Connect to Exchange Online through PowerShell.
  2. Enter the command “Add-PublicFolderClientPermission "\FolderName" -AccessRights CreateItems -User Anonymous” (provide your public folder name in place of \FolderName).


Public Folder in Office 365

Public Folders in Office 365 is designed for shared access and provide an effective way to collaborate in your Organization. It can be accessed by multiple users depending upon the permission given from the Exchange Admin Center.
Public Folder is available on Outlook on the web, Outlook 2007 or later and on Outlook for Mac.
Note: Before creating a Public Folder from Exchange, you first need to create a public folder mailbox. Public folder mailboxes contain the hierarchy of information and content for public folders.

Create a Public Folder Mailbox:


From Exchange Admin Center, go to Public folders > Public folder mailboxes > Click Add (+).




Creating Public Folder mailbox through PowerShell.

a.       Connect to Exchange Online through PowerShell.
b.       Enter the command “New-Mailbox -PublicFolder -Name <Name>”, provide the name of the public folder mailbox in place of Name.
c.       As I had already created Public_Folder as a public folder mailbox, if I try to create a new one from the PowerShell, it will be a secondary hierarchy public folder mailbox. Below I had created a new one with the name of “twitter”.



Creating a Public Folder:

Creating a Public Folder through EAC.

a.     Go to Public folders > Public folders (on the right-hand side)
b.     Click Add (+) and give a name to the Public folder.


Creating a Public Folder through PowerShell.

a.     Connect to Exchange Online through PowerShell.
b.     Enter command “New-PublicFolder -Name twitter”, this commands create a public folder on the parent path.



Mail-enabled Public Folder: Once you have created a public folder, you can mail-enable it which will allow users to post to the public folder by sending an email message. When the public folder is mail-enabled additional settings to become available. For example: Mail delivery options, mail delegation, etc.

Using EAC to mail-enabled Public Folder:

a.    Navigate to Public Folder > Public Folders.
b.    Select the Public folder for which you want to mail-enabled.
c.    In the details pane, Mail settings, click Enable.


d. To check other additional settings, select the Public Folder and click Edit.


Mail-Enable Public Folder through PowerShell.

a.     Connect to Exchange Online through PowerShell.
b.     Enter command “Enable-MailPublicFolder -Identity \twitter




Public Folder Permissions: You can add or remove users who can access the public folder and you can also edit the permission level.

1. Go to EAC > Public Folders > Public Folders.
2. Select the Public Folder for which you want to provide access to a user and edit the permission level. 
3. In the details pane, go to Folder permissions > Manage.


4. For editing the Permission level, click on the user added and then click Edit.





Monday, June 24, 2019

Can't verify domain in Office 365? Lets try this step.

Domain verification in Office 365 is a very simple task, you just need to add a custom domain, add the TXT or MX record by provided by your tenant with your domain registrar and then verify it.
However, sometime you might face issues verifying a domain and end up getting an error like "We have confirmed that you own <DOMAIN_NAME>, but we cannot add it to this tenant at this time. The domain is already added to a different Office 365 tenant".


When you are unable to verify your domain through Office 365, you can also try adding domain from Azure Active Directory.


Basically, If you already manage a tenant with Azure services or Office 365, you cannot add a custom domain name if it is already verified in another Azure AD tenant. What we can do over here is to use the ForceTakeover option with Azure AD PowerShell.


  1. Connect to Microsoft online services.


  2. Get the domain list currently associated with your O365 tenant.


  3. Add the domain which you want to verify and after adding that domain, you can see the status and it will be in the 'unverified' stage.


  4. Now, you have to get the DNS TXT record for the domain. Verification sometimes might now happen immediately because it takes time for the record to propagate.


  5.  Once you had added the DNS TXT record to your domain registrar, now you can go ahead and run the command for ForceTakeover.

  6. Add the -ForceTakeover needs to be added to the cmdlet only when .forcing an external admin takeover. This method can be used at last after you have tried each method for verifying your domain but still can't verify it.


  7. Once you run the -ForceTakeover cmdlet, the status of the domain will get verified.


Tuesday, June 11, 2019

Configure Notifications on Microsoft Teams mobile app

Whether you prefer any chat options available across the markets, if it is not user-friendly, it won’t make any sense. For being user-friendly, the first and foremost requirement is the notifications. Of course, you would not want the hassle of logging and checking into the app every moment. So, we all rely heavily on notifications on the chat to persuade us to open it. 

You can refer my blog on Microsoft Teams notification here.

It is also a fact that you will not be always online on your system, so the notifications must come on your MS Teams mobile app as well. So, I just realized today that from few days I am not getting notifications on my mobile app. I went to Teams and checked that the notifications have been set to ON but still, I am unable to receive notifications when my mobile is locked or I am not getting the floating notifications.



I went under Notifications and there is an option to configure notifications.

You will be redirected to Microsoft Teams App notifications and from here you can choose for which features (Chat, Incoming Calls, etc) you want to turn on which type of notifications (Floating notifications, Lock screen notifications, etc) and accordingly turn it ON (See below image).




You can also navigate to Microsoft Teams App Settings from your phone Settings > Notification & Status bar > App Notifications.  Under App notifications option, you will be able to see the list of applications installed on your phone and from there choose Microsoft Teams.




Hope this article helps. ThankYou!



Friday, May 31, 2019

Microsoft Teams integration with Dynamics 365 for Customer Engagement apps


Before getting into details, firstly I would like to talk about Microsoft Teams. If you’re familiar with MS Teams, you know that it is chat and collaboration platform – a place to manage all your conversations, files and important tools in one team workspace. You can access SharePoint, Power Bi and now Dynamics 365 for Customer Engagement right from the Teams app and can collaborate. Microsoft Teams comes with the Office 365 subscription and is present with both web and desktop version as well.
Dynamics 365 page can be added as a tab on Microsoft Teams channel they are working on to allow easy access to the customer information. The tab added on MS Teams channel is a fully functional page that means you can edit any records or navigate to related records without leaving the app. You can also use Dynamics 365 Bot for quick updates on records.

Enable Microsoft Teams integration feature from Dynamics 365 Customer Engagement:
  1. Sign in as a System Administrator.
  2. Go to Settings > Administration > System Settings > General tab
  3. Enable Microsoft Teams integration.

Let's get started:
  1.  I hope you already have Microsoft Teams App installed on your system.
  2. Go to the Teams channel where you want to add a Dynamics 365 page as a tab, add a tab by clicking on the + button.

  3. Search for Dynamics 365 App.

  4. After clicking on the Dynamics 365 App, you will be asked to select the Organization and the App module. Select the same from the dropdown accordingly and click on SELECT.
  5. Search for the entity, you want to connect them to this channel and click on SAVE.
  6. It is done, you can now edit the record details or navigate to the related records in Dynamics 365 from MS Teams app.
  7. Once you complete the above steps, you will see a notification of record is successfully connected (see above image). Any changes done here will be synchronized with the Dynamics 365 for Customer Engagement apps.
  8. Once the integration is done, Teams also provides the feature to associate files. Any related documents uploaded in the Files tab in Microsoft Teams will also appear in D365 Customer Engagement apps under Documents for the record. Similarly, any documents added in D365 for Customer Engagement apps will appear in the Files tab on Microsoft Teams.

    Below images is of Microsoft Teams Files tab:

    Below image is of D365 for CE app > Documents:


    In the below images, you can see various locations for documents, this is because I have also enabled SharePoint integration. You can select the specific location or All File to view each file related to this record. As you can see in the below images the files uploaded on Microsoft Teams appears over here.


  9. If you want open a record in Dynamics 365 for CE and you are in Microsoft Teams currently, don’t bother to enter the URL. Click the Go to Website icon.

Hope this article helps you in integrating your D365 for CE apps records with Microsoft Teams, so you can easily access the records and make changes to it through Microsoft Teams and collaborate easily on the records through Teams.


Monday, May 27, 2019

Microsoft enhances the Google G Suite to Office 365 migration experience

At the end of 2018, Microsoft has announced about the new Google G Suite to Office 365 migration tool and now it is here. Microsoft has rolled out this new tool which enhances the migration process from G Suite to Office 365.

This Perform G Suite to Office 365 migration documentation from Microsoft, provides you with the steps to perform the staged migration. There was already a way which is IMAP migration to perform migration from G Suite or any other IMAP email system to Office 365 but this option doesn't migrate contacts or calendar items. With this G Suite migration tool, contacts and calendar items also get migrated. 


Mail data will be migrated using the IMAP protocol with this G Suite migration tool. Below data will not be migrated with this tool -
  • Shared calendars, cloud attachments will not get migrated.
  • Three email addresses per contact are migrated.
  • Gmail tags and custom tags are not migrated over.
  • Room bookings.
  • Automatic reply settings.
Advantages of migration using this tool:
  • There will be no additional costs like some third-party migration solutions require.
  • Migrate your mail, calendar, and contacts.
  • Account authentications - No need to have or reset user credentials to migrate their data.
  • Built-in mechanisms to optimize storage by reducing the item duplications as the Labels are converted to Folders.
Looking forward to using this tool for migrating Google G Suite users to Office 365 in the future. I will definitely be going to share my experience in the future.



Thursday, May 16, 2019

Document ID for Record Management in SharePoint Online

Introduction:


As you know that SharePoint Online can be used as a document management platform and with the help of Document Id's you can effectively manage your documents by providing an easy way to track irrespective of their location. Document Id's are automatically assigned to the documents uploaded on document or record management platform.

Before using the Document ID features for our document management system, you must enable it for each site collection in which your documents are located.

You must be a Site Collection Administrator for enabling this feature in SPO.

Activate, enable and configure Document ID's:

  1. Go to the top-level Site collection > Site Settings.
  2. Under Site Collection Administration, click Site collection features.



  3. Next to Document ID, click Activate. Activate icon will appear and the feature is activated.

  4. Go back to the Site Settings page and under Site Collection Administration, select Document ID settings.

  5. You will have to assign a prefix for the Document ID's and the prefix should be between 4 to 12 characters with no special character.


  6. If you want all the documents within the Site Collection, to be assigned with a Document ID with the specified prefix, check the box "Reset all Document ID's" (See above image).
  7. Once this feature is enabled, any new document created or uploaded to any document library in this particular Site Collection received a unique Document ID.

  8. Document Id's can be viewed from the document properties, these are the hyperlinks that you can copy and use it to open a document in Office.

Moving and Copying a file with a Document ID:


When you move a file in SharePoint Online, Document ID will move with the file. It basically depends on whether the service is enabled or not at the destination site. So, if the service is not enabled at that site then the document will no longer have the Document ID.

When a copy of the document is made, a new Document ID is created for the copy and obviously, the service needs to be enabled at the site where you are copying the file.





Tuesday, May 7, 2019

Manage Microsoft Teams through PowerShell (Microsoft Teams PowerShell Module)

Introduction:


In this article, we are going to take a quick overview of the Microsoft Teams PowerShell module and will cover few things which we can perform in Microsoft Teams with the help of PowerShell.

There are two different PowerShell modules to manage Microsoft Teams.

  1. Microsoft Teams PowerShell Module – You can get this module from here https://www.powershellgallery.com/packages/MicrosoftTeams/1.0.0
  2. Skype for Business PowerShell Module – You can download it from here https://www.microsoft.com/en-us/download/details.aspx?id=39366
Teams PowerShell module contain all the cmdlets needed to create and manage teams whereas Skype for Business the module contains the cmdlets to manage policies, configuration, and other tools.

Connecting to Microsoft Teams PowerShell:

  1. Install the Microsoft Teams PowerShell Module. Open Windows PowerShell and run command “Install-Module -Name MicrosoftTeams” and then enter Y.



    The module was already installed on my system, that’s why I get the messages in highlighted in the above image. The version was old, so I re-entered the command and added the -Force parameter “Install-Module -Name MicrosoftTeams -Force
  2. Connect with Microsoft Teams. Run command “Connect-MicrosoftTeams” and enter the credentials.


    After login, you will be able to see your tenant details.

    1. After the PowerShell Module relates to your Microsoft Teams, you can use the cmdlets for creating and managing teams.

      For e.g, To get all your teams list, run command “Get-Team



      For creating a new team, run command “New-Team



      For managing Team users, run a command “Add-TeamUser”. You will be asked to provide GroupId.


      After providing the GroupId, it will ask to provide the user, which needs to be added to the team.


    2. Similarly, you can remove the user from a team, create new channel or remove any team channel or else remove any group, etc. All these cmdlets can be run as end users, but it will only work for the teams you own, or you are a member of but as a global admin, you will be able to act on all the teams.

    Managing MS Teams policies via PowerShell:

    1. Download and install Skype for Business PowerShell Module.

    2. Connect with Skype for Business PowerShell Module. Open Windows PowerShell and run the following commands:

             Import-Module SkypeOnlineConnector”
        “$userCredential = Get-Credential”


             “$sfbSession = New-CsOnlineSession -Credential $userCredential”
             “Import-PSSession $sfbSession”

      Now you are connected to Skype for Business PowerShell Module.

    3. There are basically 5 commands to manage the policies.
      ·         GET – Get the details of the policy.
      ·         NEW – Create new policies.
      ·         SET – Lets you set particular values on a given policy.
      ·         REMOVE – Delete the customs policy.
      ·         GRANT – Assign the policy to a particular user.

      For e.g, you want to get the details of all the meeting policy, run command “Get-CsTeamsMeetingPolicy


      You will be able to get the details of all the meeting policy whether it has been created by Microsoft or it is a custom policy that will be shown.

      Similarly, for Messaging policy run command “Get-CsTeamsMessagingPolicy

    Managing configurations via PowerShell:

    1. Connect to Skype for Business PowerShell Module. You have seen above how to connect to Skype for Business PS Module.
    2. Run command “Get-CsTeamsClientConfiguration”. This is basically your Teams settings in the admin center.



    Change the default email address and anonymous user to send email to Public Folder

    An Exchange public folder can be used by several people in Outlook Web App or in their local Outlook installations. It allows a group of us...