Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also .

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also .
Choose a Base Repository
crpietschmann/azure-docs
MicrosoftDocs/azure-docs
APiZFiBlockChain4/azure-docs
ARYANKAUSHIK/azure-docs
Angelaliu10/azure-docs
AnthonySteven/azure-docs
ArvindHarinder1/azure-docs
AzureSupport/azure-docs
Banani-Rath/azure-docs
BretStateham/azure-docs
CNXTEoEorg/azure-docs
CarlRabeler/azure-docs
DRediske/azure-docs
DaleKoetke/azure-docs
DieterRa/azure-docs
DuncanmaMSFT/azure-docs
Erikre/azure-docs
Gamlyn/azure-docs
JakobGSvendsen/azure-docs
Jolleyman/azure-docs
JulianoCristian/azure-docs
JuniorIce/azure-docs
KumudD/azure-docs
LuisCabrer/azure-docs
MaggiePucciEvans/azure-docs
MattAllison/azure-docs
MatthewMcGlynn/azure-docs
MeganYount/azure-docs
Meladie/azure-docs
MelissaALowe/azure-docs
MikkelHegn/azure-docs
PeterSelchDahl/azure-docs
RPangrle/azure-docs
Ryansoc/azure-docs
SanderBerkouwer/azure-docs
Security8technology/azure-docs
SmallRug/azure-docs
StephenWThomas/azure-docs
TomShinder/azure-docs
VKsai/azure-docs
Vashum/azure-docs
YoannGUILLO/azure-docs
YusufGarba/azure-docs
abhi004/azure-docs
adkinn/azure-docs
admingagan/azure-docs
aggFTW/azure-docs
ahgyger/azure-docs
ajith-k/azure-docs
alexandair/azure-docs
alkohli/azure-docs
alvarorahul/azure-docs
amitbapat/azure-docs
anavinahar/azure-docs
andreasgloor/azure-docs
andredm7/azure-docs
andreyse/azure-docs
andyjballgit/azure-docs
anthonychu/azure-docs
anwather/azure-docs
aoancea/azure-docs
arafato/azure-docs
ashishthaps/azure-docs
avranju/azure-docs
azuredatafactoryv2/azure-docs
baseif/azure-docs
becczhang/azure-docs
benilg/azure-docs
bjarnesl/azure-docs
brendalee/azure-docs
brendandburns/azure-docs
brunolewin-msft/azure-docs
bvanderb/azure-docs
chainoy/azure-docs
chongok88/azure-docs
cloudmelon/azure-docs
colemickens/azure-docs
ctolkien/azure-docs
cychua/azure-docs
damianotway/azure-docs
darrelmiller/azure-docs
davidmarek/azure-docs
davidmarekmsft/azure-docs
devlead/azure-docs
dfberry/azure-docs
dmitrykazakov/azure-docs
doneladams/azure-docs
dougvdotcom/azure-docs
dreijer/azure-docs
ejarvi/azure-docs
eloldag/azure-docs
enuysa-msft/azure-docs
erensarisaltik/azure-docs
ernestcr/azure-docs
fabiocav/azure-docs
fahey252/azure-docs
falabs/azure-docs
fashaikh/azure-docs
faxata/azure-docs
fenxu/azure-docs
fixx220/azure-docs
fleetzen/azure-docs
friism/azure-docs
ggailey777/azure-docs
giridham/azure-docs
gopitk/azure-docs
gusfraser/azure-docs
h0n/azure-docs
harishkunal88/azure-docs
haristauqir/azure-docs
hazwan90/azure-docs
hvredevoort/azure-docs
ilyas-it83/azure-docs
ishepherd/azure-docs
j-thomas-ucl/azure-docs
jaymathe/azure-docs
jboeshart/azure-docs
jeffhollan/azure-docs
jguadagno/azure-docs
jimdial/azure-docs
jimeilong/azure-docs
jkewley/azure-docs
johnthcall/azure-docs
jolleymd/azure-docs
jtucker/azure-docs
kencenerelli/azure-docs
kevinlam1/azure-docs
kevinvngo/azure-docs
kevinyr/azure-docs
khilscher/azure-docs
ksens/azure-docs
kwill-MSFT/azure-docs
kyddjamFoundation/azure-docs
laramume/azure-docs
larslind/azure-docs
lastcoolnameleft/azure-docs
leyasa/azure-docs
lzandman/azure-docs
mabicca/azure-docs
makhaly/azure-docs
manuaery/azure-docs
masnider/azure-docs
matt-softlogic/azure-docs
mayanknayar/azure-docs
miaojiang/azure-docs
micurd/azure-docs
mikeplavsky/azure-docs
mimig1/azure-docs
misteed-msft/azure-docs
mohamed-mrad/azure-docs
msmbaldwin/azure-docs
nathan-gs/azure-docs
nickarms/azure-docs
nromyn/azure-docs
obsoleted/azure-docs
oedenfield/azure-docs
ovishesh/azure-docs
p2horst/azure-docs
pavinan/azure-docs
pirminf/azure-docs
pollirrata/azure-docs
psignoret/azure-docs
qanon1111/azure-docs
qm31122016/azure-docs
rachel-msft/azure-docs
raiye/azure-docs
randycampbell/azure-docs
raymondlaghaeian/azure-docs
rboucher/azure-docs
rdtechie/azure-docs
rogeriorrodrigues/azure-docs
rverschuur/azure-docs
saipv/azure-docs
selhorn/azure-docs
sfilinto/azure-docs
sharonlo101/azure-docs
shashishailaj/azure-docs
shchoy/azure-docs
shrishrirang/azure-docs
simplesteph/azure-docs
soelu/azure-docs
stefanogiacco/azure-docs
steven-r/azure-docs
sujitks/azure-docs
symphonyeyc/azure-docs
tamiam/azure-docs
themacmarketer/azure-docs
themichaelbender/azure-docs
thumperBIG/azure-docs
toyashwantsingh/azure-docs
tsubasaxZZZ/azure-docs
vitorfariatomaz/azure-docs
vkonev/azure-docs
vladimir-kotikov/azure-docs
voellm/azure-docs
vtango/azure-docs
vwxyzh/azure-docs
webash/azure-docs
wshirey/azure-docs
wyldebill/azure-docs
xstabel/azure-docs
Nothing to show
Choose a Head Repository
crpietschmann/azure-docs
MicrosoftDocs/azure-docs
APiZFiBlockChain4/azure-docs
ARYANKAUSHIK/azure-docs
Angelaliu10/azure-docs
AnthonySteven/azure-docs
ArvindHarinder1/azure-docs
AzureSupport/azure-docs
Banani-Rath/azure-docs
BretStateham/azure-docs
CNXTEoEorg/azure-docs
CarlRabeler/azure-docs
DRediske/azure-docs
DaleKoetke/azure-docs
DieterRa/azure-docs
DuncanmaMSFT/azure-docs
Erikre/azure-docs
Gamlyn/azure-docs
JakobGSvendsen/azure-docs
Jolleyman/azure-docs
JulianoCristian/azure-docs
JuniorIce/azure-docs
KumudD/azure-docs
LuisCabrer/azure-docs
MaggiePucciEvans/azure-docs
MattAllison/azure-docs
MatthewMcGlynn/azure-docs
MeganYount/azure-docs
Meladie/azure-docs
MelissaALowe/azure-docs
MikkelHegn/azure-docs
PeterSelchDahl/azure-docs
RPangrle/azure-docs
Ryansoc/azure-docs
SanderBerkouwer/azure-docs
Security8technology/azure-docs
SmallRug/azure-docs
StephenWThomas/azure-docs
TomShinder/azure-docs
VKsai/azure-docs
Vashum/azure-docs
YoannGUILLO/azure-docs
YusufGarba/azure-docs
abhi004/azure-docs
adkinn/azure-docs
admingagan/azure-docs
aggFTW/azure-docs
ahgyger/azure-docs
ajith-k/azure-docs
alexandair/azure-docs
alkohli/azure-docs
alvarorahul/azure-docs
amitbapat/azure-docs
anavinahar/azure-docs
andreasgloor/azure-docs
andredm7/azure-docs
andreyse/azure-docs
andyjballgit/azure-docs
anthonychu/azure-docs
anwather/azure-docs
aoancea/azure-docs
arafato/azure-docs
ashishthaps/azure-docs
avranju/azure-docs
azuredatafactoryv2/azure-docs
baseif/azure-docs
becczhang/azure-docs
benilg/azure-docs
bjarnesl/azure-docs
brendalee/azure-docs
brendandburns/azure-docs
brunolewin-msft/azure-docs
bvanderb/azure-docs
chainoy/azure-docs
chongok88/azure-docs
cloudmelon/azure-docs
colemickens/azure-docs
ctolkien/azure-docs
cychua/azure-docs
damianotway/azure-docs
darrelmiller/azure-docs
davidmarek/azure-docs
davidmarekmsft/azure-docs
devlead/azure-docs
dfberry/azure-docs
dmitrykazakov/azure-docs
doneladams/azure-docs
dougvdotcom/azure-docs
dreijer/azure-docs
ejarvi/azure-docs
eloldag/azure-docs
enuysa-msft/azure-docs
erensarisaltik/azure-docs
ernestcr/azure-docs
fabiocav/azure-docs
fahey252/azure-docs
falabs/azure-docs
fashaikh/azure-docs
faxata/azure-docs
fenxu/azure-docs
fixx220/azure-docs
fleetzen/azure-docs
friism/azure-docs
ggailey777/azure-docs
giridham/azure-docs
gopitk/azure-docs
gusfraser/azure-docs
h0n/azure-docs
harishkunal88/azure-docs
haristauqir/azure-docs
hazwan90/azure-docs
hvredevoort/azure-docs
ilyas-it83/azure-docs
ishepherd/azure-docs
j-thomas-ucl/azure-docs
jaymathe/azure-docs
jboeshart/azure-docs
jeffhollan/azure-docs
jguadagno/azure-docs
jimdial/azure-docs
jimeilong/azure-docs
jkewley/azure-docs
johnthcall/azure-docs
jolleymd/azure-docs
jtucker/azure-docs
kencenerelli/azure-docs
kevinlam1/azure-docs
kevinvngo/azure-docs
kevinyr/azure-docs
khilscher/azure-docs
ksens/azure-docs
kwill-MSFT/azure-docs
kyddjamFoundation/azure-docs
laramume/azure-docs
larslind/azure-docs
lastcoolnameleft/azure-docs
leyasa/azure-docs
lzandman/azure-docs
mabicca/azure-docs
makhaly/azure-docs
manuaery/azure-docs
masnider/azure-docs
matt-softlogic/azure-docs
mayanknayar/azure-docs
miaojiang/azure-docs
micurd/azure-docs
mikeplavsky/azure-docs
mimig1/azure-docs
misteed-msft/azure-docs
mohamed-mrad/azure-docs
msmbaldwin/azure-docs
nathan-gs/azure-docs
nickarms/azure-docs
nromyn/azure-docs
obsoleted/azure-docs
oedenfield/azure-docs
ovishesh/azure-docs
p2horst/azure-docs
pavinan/azure-docs
pirminf/azure-docs
pollirrata/azure-docs
psignoret/azure-docs
qanon1111/azure-docs
qm31122016/azure-docs
rachel-msft/azure-docs
raiye/azure-docs
randycampbell/azure-docs
raymondlaghaeian/azure-docs
rboucher/azure-docs
rdtechie/azure-docs
rogeriorrodrigues/azure-docs
rverschuur/azure-docs
saipv/azure-docs
selhorn/azure-docs
sfilinto/azure-docs
sharonlo101/azure-docs
shashishailaj/azure-docs
shchoy/azure-docs
shrishrirang/azure-docs
simplesteph/azure-docs
soelu/azure-docs
stefanogiacco/azure-docs
steven-r/azure-docs
sujitks/azure-docs
symphonyeyc/azure-docs
tamiam/azure-docs
themacmarketer/azure-docs
themichaelbender/azure-docs
thumperBIG/azure-docs
toyashwantsingh/azure-docs
tsubasaxZZZ/azure-docs
vitorfariatomaz/azure-docs
vkonev/azure-docs
vladimir-kotikov/azure-docs
voellm/azure-docs
vtango/azure-docs
vwxyzh/azure-docs
webash/azure-docs
wshirey/azure-docs
wyldebill/azure-docs
xstabel/azure-docs
Nothing to show
  • 1 commit
  • 1 file changed
  • 0 commit comments
  • 1 contributor
Commits on Jul 24, 2018
Showing with 2 additions and 2 deletions.
  1. +2 −2 articles/active-directory/develop/active-directory-graph-api.md
@@ -55,8 +55,8 @@ Azure AD Graph API provides the following features:
## Scenarios
Azure AD Graph API enables many application scenarios. The following scenarios are the most common:
* **Line of Business (Single Tenant) Application**: In this scenario, an enterprise developer works for an organization that has an Office 365 subscription. The developer is building a web application that interacts with Azure AD to perform tasks such assigning a license to a user. This task requires access to Azure AD Graph API, so the developer registers the single tenant application in Azure AD and configures read and write permissions for Azure AD Graph API. Then the application is configured to use either its own credentials or those of the currently sign-in user to acquire a token to call Azure AD Graph API.
* **Software as a Service Application (Multi-Tenant)**: In this scenario, an independent software vendor (ISV) is developing hosted multi-tenant web application that provides user management features for other organizations that use Azure AD. These features require access to directory objects, and so the application needs to call Azure AD Graph API. The developer registers the application in Azure AD, configures it to require read and write permissions for Azure AD Graph API, and then enables external access so that other organizations can consent to use the application in their directory. When a user in another organization authenticates to the application for the first time, they are shown a consent dialog with the permissions the application is requesting. Granting consent will then give the application those requested permissions to Azure AD Graph API in the user’s directory. For more information on the consent framework, see [Overview of the Consent Framework](active-directory-integrating-applications.md).
* **Line of Business (Single Tenant) Application**: In this scenario, an enterprise developer works for an organization that has an Office 365 subscription. The developer is building a web application that interacts with Azure AD to perform tasks such as assigning a license to a user. This task requires access to the Azure AD Graph API, so the developer registers the single tenant application in Azure AD and configures read and write permissions for Azure AD Graph API. Then the application is configured to use either its own credentials or those of the currently sign-in user to acquire a token to call the Azure AD Graph API.
* **Software as a Service Application (Multi-Tenant)**: In this scenario, an independent software vendor (ISV) is developing a hosted multi-tenant web application that provides user management features for other organizations that use Azure AD. These features require access to directory objects, so the application needs to call the Azure AD Graph API. The developer registers the application in Azure AD, configures it to require read and write permissions for Azure AD Graph API, and then enables external access so that other organizations can consent to use the application in their directory. When a user in another organization authenticates to the application for the first time, they are shown a consent dialog with the permissions the application is requesting. Granting consent will then give the application those requested permissions to Azure AD Graph API in the user’s directory. For more information on the consent framework, see [Overview of the Consent Framework](active-directory-integrating-applications.md).
## See Also
[Azure AD Graph API Quickstart Guide](active-directory-graph-api-quickstart.md)

No commit comments for this range