Skip to main content

Update to generating App Password in Office 365 / Microsoft 365

Introduction:

In my previous blog on setting up the App Password for Outlook after enabling Multi-Factor Authentication, refer to How to bypass Multi-Factor Authentication
This blog is an update on the changes made to the process creation of App Password and is relatively easier to follow.
I faced an issue where the 'View Privacy Link' button was missing in Settings & Privacy > Privacy
View Privacy Link Missing - Office 365 / Microsoft 365

 

Pre-requisites:

Microsoft 365 (a.k.a Office 365)

Demonstration:

In portal.office.com, go to the Users icon on the top right and select 'View Account'

View Account


Head over to the 'Security Info' navigation on the left side and click on 'Add Method
Adding Method in Security Info


You need to select the Method as 'App Password', provide the 'App Name' and copy the password generated for further use
Adding a Method

Adding AppName


Copying App Password


I tested the copied password in SMTP Mail Setup in Business Central and it worked like a charm.

Conclusion:

While working on the method to generate App Password as per my previous blog, I realized that the option wasn't visible. Hence, I  found this way to resolve the query.

Thanks for reading 

Comments

  1. Great tutorial, this blog is awesome to learn about MS office from installation, Office Setup and other tiny problems one may come across. Thank you for posting this educative post.

    ReplyDelete
  2. Thanks. Feel free to suggest if you need more blogs on any specific topics.

    ReplyDelete

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe