MENU
Can you map the Okta user ID as an Office 365 Immutable ID?
Solution: Done via mappings, by pushing from Okta to Office 365: user.getInternalProperty("id")
Suggested Answer: A
Get Premium Okta Certified Administrator Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
FI
Filiberto
12 months ago
Totally agree, this is how we do it!
LA
Laurena
12 months ago
I thought Immutable ID was different from user ID.
EU
Eulah
12 months ago
Wait, are you sure that works for all cases?
TI
Tiera
1 year ago
That's right, just use user.getInternalProperty("id").
SO
Solange
1 year ago
Yes, you can map it!
CL
Clemencia
1 year ago
I feel like this question came up in our last review session, and I think the answer was "Yes" based on how mappings work.
IS
Isreal
1 year ago
I believe the solution involves using the user.getInternalProperty("id") function, but I might need to double-check that.
BU
Buck
1 year ago
I remember practicing a similar question where we discussed user attributes in Okta, but I can't recall the specific property to use for the mapping.
AL
Alpha
1 year ago
I think we can map the Okta user ID to the Immutable ID in Office 365, but I'm not entirely sure about the exact method.
KA
Kara
1 year ago
Hmm, I'm a bit confused on the distinction between the ADM being iterative within the first cycle versus between phases. I'll need to review my notes to clarify that.
BL
Blair
1 year ago
I'm a bit unsure about this one. The pipe character is used to connect different parts of a search query, but I'm not sure if it's specifically before clauses, commands, arguments, or functions. I'll have to think about this a bit more.
OR
Oren
1 year ago
I'm unsure, but I think steepening means short-term rates fall relative to long-term rates? That doesn't sound right, though.