Can't click to dial from outlook 365 ios app anymore?

Anonymous
2019-10-14T20:17:38+00:00

When dialing in to conference calls from my Outlook 365 app I have always been able to just click on the number in the "location" field of calendar meetings.  However, after the ios 13 update I can no longer click on numbers and am having to enter them manually!  Sometimes this involves not just the 10 digit phone number, but a long "conference code" number as well, all of which was previously dialed with one easy click.

Is there any way I can get that functionality back?  I need to be able to dial directly from outlook invites.  That's the primary benefit of using them.

Outlook | Outlook for mobile | Outlook for iOS | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

50 answers

Sort by: Newest
  1. Anonymous
    2019-11-14T19:46:57+00:00

    This started working again after a combined ios and outlook update about 3 weeks ago. Since both updates came out within a day of one another I can’t say for sure but it appears to have been fixed with the outlook release. 

    The organization I work for was informed that this functionality was intentionally disabled due to privacy concerns, and then re-enabled due to massive outcry from many customers. 

    Map locations still do not work however, even though there is a map setting within outlook.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-11-14T19:31:51+00:00

    Did you ever get a resolution to this? This is exactly the issue my office is experiencing. We schedule all meetings from desktop then use the app to either make a call or get directions to next meeting. The last month or so, this has stopped working completely. We cannot click on addresses (that are usually copy or pasted from Google or an address book) and we cannot click on phone numbers to directly call the number on an appointment. This is making us consider switching away from Outlook. 

    If you found a solution, please let me know. Went through the same "show me the evidence" routine from Office 365 support and they have been NO help.

    Thanks!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-11-14T18:56:33+00:00

    Interesting. What IOS version and which iPhone are you using? My iPhone XS and iPhone 8 are both working fine on Outlook version 4.11.0 on IOS 13.2.2. I have tested with numerous calendar invites using phone numbers and addresses in the location field with no issues. Maybe try a hard reset?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-11-14T18:21:35+00:00

    Not sure that this is a correct statement of the issue is resolved.

    I had it working prior to 4.11.0 and now no phone numbers or any type of link will work in a calendar invite.

    I do agree that Microsoft should vet these updates better before releasing them to the public and as you state trouble shoot an issue that was introduced with the latest release.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-11-13T04:05:40+00:00

    The issue has been resolved in Outlook version 4.11.0. Tap to dial and “tap to maps” both work. Thank you for fixing this issue and please make sure it keeps working, Microsoft.

    Your user community would appreciate it if Microsoft would have better communication with its customers regarding these types issues. There are no updates here or on the Microsoft forum. Zero communication from Microsoft. The app version history in the App Store doesn’t fess up and list any bugs. Have you considered taking the time to list out the specific bug fixes like other developers do?? We understand issues arise and it’s very difficult to anticipate every bug, but just have some transparency and accountability. Don’t make your customers run around in circles with tech support for 2 weeks to be told “the app is performing as designed”, when clearly it’s not. You have the resources to minimize these issues, so please do something about it.

    Was this answer helpful?

    0 comments No comments