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: Most helpful
  1. Anonymous
    2019-10-30T03:57:09+00:00

    Hello All,

    Microsoft has "seemed" to fix the issue!

    I have an iPhone 11 Pro that is running iOS 13.2 and Outlook app version 4.9.0, I can tap on the number in the location field and it box pops up asking if I want to call the number.

    I also have a iPhone 7 this is running 13.1.3 and Outlook app version 4.9.0, I am able to tap on the location field and call the number.

    Looks like iOS doesn't seem to effect the app function. 

    I tested an old version of the Outlook app (version 4.6.0) on iPad and was unable to click on the number but after I updated the app to version 4.9.0, I was able to click on the number and call it.

    So, update your guys Outlook app to 4.9 and see if you can tap on the number.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-10-29T23:40:50+00:00

    I'm skeptical of the claim that this issue is intended functionality. The reason I'm skeptical is because address data placed into this field is also not functioning. Invites sent from Outlook on the desktop, which place properly formatted addresses (such as 123 Blue Street, Louisville, KY, 37203) do not respond to a tap when the calendar invite is brought up on Outlook for iOS. Responding to a tap of an accurate address is obviously intended functionality, and it is currently missing in the most recent version of Outlook for iOS.

    However, if I originate the calendar invite on Outlook for iOS, when I go to enter a location on the invite, a new flow presents that shows me a map. When I finalize the address, a picture of the map appears alongside the address in my invite. When I send the invite using this flow on Outlook for iOS, and the recipient views it on Outlook for iOS, the address is clickable (they also see an image of a map as well).

    Obviously the intended functionality of the location field is to bring up a map if any properly formatted address appears, regardless of how it was formatted when entered.

    To me it seems like the location field has been fundamentally broken in Outlook for iOS. Any support rep that tells you your click-to-dial issue is "intended functionality" should answer to why valid addresses that appear in the location field also are not able to be tapped to launch a map. Do they really think not looking up addresses is "intended functionality"? Escalate that.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-10-29T18:38:11+00:00

    They are.  I have heard there are two thousand customers yelling at MS right now.  But I just tested an iPhone 8 with 12.4.1 and it did not work there either.  this is something bigger.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-10-29T18:32:34+00:00

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-10-29T18:12:34+00:00

    <sigh> When I saw the “it’s fixed in 13.2” comment from a TAM above, I was pretty sure this was just a guess or a delay tactic. Thanks @ryandawson2 for the confirmation this is not a resolution to the problem.

    This only happens in Outlook for iOS. And, if it was truly a privacy concern to let iOS dial a number from an entry in the location field of an outlook appointment, then why does this functionality work from within the body of an Outlook email, or within a contact entry in Outlook, or from the description field of an Outlook appointment?

    I do hope someone from MSFT is monitoring this discussion. I work with an organization of 60k+, where iOS is very common for mobile devices, and things are heating up quickly. Any organization with a highly mobile workforce will be impacted by this new “intended functionality” decision. The excuse that it’s an IOS issue is falling flat given it worked fine in iOS 13 one day and then didn’t after outlook was upgraded “without” any iOS upgrade.

    Was this answer helpful?

    0 comments No comments