You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory
21
21
22
-
Azure Active Directory (Azure AD) lets you automate the creation, maintenance, and removal of user identities in cloud ([SaaS](https://azure.microsoft.com/overview/what-is-saas/)) applications such as Dropbox, Salesforce, ServiceNow, and more. This is known as automated user provisioning for SaaS apps.
22
+
Azure Active Directory (Azure AD) lets you automate the creation, maintenance, and removal of user identities in cloud SaaS applications such as [Dropbox](https://docs.microsoft.com/azure/active-directory/saas-apps/dropboxforbusiness-provisioning-tutorial), [Salesforce](https://docs.microsoft.com/azure/active-directory/saas-apps/salesforce-provisioning-tutorial), [ServiceNow](https://docs.microsoft.com/azure/active-directory/saas-apps/servicenow-provisioning-tutorial), and more. This is known as automated user provisioning for SaaS apps.
@@ -85,11 +85,7 @@ Use the Azure Active Directory portal to configure the Azure AD provisioning ser
85
85
86
86
1. Open the **[Azure Active Directory portal](https://aad.portal.azure.com)**.
87
87
1. Select **Enterprise applications** from the left pane. A list of all configured apps is show.
88
-
1. Choose **+ New application** to add an application. Add either of the following depending on your scenario:
89
-
90
-
- The **Add your own app** option supports custom-developed SCIM integrations.
91
-
- All applications in the **Add from the gallery** > **Featured applications** section support automatic provisioning. See the [list of application tutorials for user provisioning](../saas-apps/tutorial-list.md) for additional ones.
92
-
88
+
1. Choose **+ New application** to add an application.
93
89
1. Provide any details and select **Add**. The new app is added to the list of enterprise applications and opens to its application management screen.
94
90
1. Select **Provisioning** to manage user account provisioning settings for the app.
Copy file name to clipboardExpand all lines: articles/active-directory/reports-monitoring/concept-provisioning-logs.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,7 +204,9 @@ The **summary** tab provides an overview of what happened and identifiers for th
204
204
205
205
## Error Codes
206
206
207
-
|ErrorCode|Description|
207
+
Use the table below to better understand how to resolve errors you may find in the provisioning logs. For any error codes that are missing, provide feedback using the link at the bottom of this page.
208
+
209
+
|Error Code|Description|
208
210
|---|---|
209
211
|Conflict, EntryConflict|Correct the conflicting attribute values in either Azure AD or the application, or review your matching attribute configuration if the conflicting user account was supposed to be matched and taken over. Review the following [documentation](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes) for more information on configuring matching attributes.|
210
212
|TooManyRequests|The target app rejected this attempt to update the user because it is overloaded and receiving too many requests. There is nothing to do. This attempt will automatically be retired. Microsoft has also been notified of this issue.|
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/tutorial-list.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,8 @@ To help integrate your cloud-enabled [software as a service (SaaS)](https://azur
26
26
27
27
For a list of all SaaS apps that have been pre-integrated into Azure AD, see the [Active Directory Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/category/azure-active-directory-apps).
28
28
29
+
Use the [application network portal](https://docs.microsoft.com/azure/active-directory/develop/howto-app-gallery-listing) to request a [SCIM](https://docs.microsoft.com/azure/active-directory/manage-apps/use-scim-to-provision-users-and-groups) enabled application to be added to the gallery for automatic provisioning or a SAML / OIDC enabled application to be added to the gallery for SSO.
30
+
29
31
## Quick links
30
32
31
33
| Logo | Application tutorial for single sign-on | Application tutorial for user provisioning |
@@ -112,4 +114,4 @@ To find more tutorials, use the table of contents on the left.
112
114
113
115
## Next steps
114
116
115
-
To learn more about application management, see [What is application management](../manage-apps/what-is-application-management.md).
117
+
To learn more about application management, see [What is application management](../manage-apps/what-is-application-management.md).
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-bindings-service-bus.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ The Service Bus bindings are provided in the [Microsoft.Azure.WebJobs.ServiceBus
28
28
29
29
## Packages - Functions 2.x
30
30
31
-
The Service Bus bindings are provided in the [Microsoft.Azure.WebJobs.Extensions.ServiceBus](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.ServiceBus) NuGet package, version 3.x. Source code for the package is in the [azure-webjobs-sdk](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs.Extensions.ServiceBus/) GitHub repository.
31
+
The Service Bus bindings are provided in the [Microsoft.Azure.WebJobs.Extensions.ServiceBus](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.ServiceBus) NuGet package, version 3.x. Source code for the package is in the [azure-functions-servicebus-extension](https://github.com/Azure/azure-functions-servicebus-extension) GitHub repository.
32
32
33
33
> [!NOTE]
34
34
> Version 2.x does not create the topic or subscription configured in the `ServiceBusTrigger` instance. Version 2.x is based on [Microsoft.Azure.ServiceBus](https://www.nuget.org/packages/Microsoft.Azure.ServiceBus) and does not handle queue management.
# Create Azure Recovery Services backup policies using REST API
15
15
16
-
The steps to create a backup policy for an Azure Recovery Services vault are outlined in the [policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies/createorupdate). Let us use this document as a reference to create a policy for Azure VM backup.
16
+
The steps to create a backup policy for an Azure Recovery Services vault are outlined in the [policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate). Let us use this document as a reference to create a policy for Azure VM backup.
17
17
18
18
## Backup policy essentials
19
19
@@ -46,10 +46,10 @@ For example, to create a policy for Azure VM backup, following are the component
For the complete list of definitions in the request body, refer to the [backup policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies/createorupdate).
52
+
For the complete list of definitions in the request body, refer to the [backup policy REST API document](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate).
53
53
54
54
### Example request body
55
55
@@ -150,11 +150,11 @@ The policy says:
150
150
151
151
The backup policy creation/update is a [asynchronous operation](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-async-operations). It means this operation creates another operation that needs to be tracked separately.
152
152
153
-
It returns two responses: 202 (Accepted) when another operation is created and then 200 (OK) when that operation completes.
153
+
It returns two responses: 202 (Accepted) when another operation is created, and then 200 (OK) when that operation completes.
154
154
155
155
|Name |Type |Description |
156
156
|---------|---------|---------|
157
-
|200 OK |[Protection PolicyResource](https://docs.microsoft.com/rest/api/backup/protectionpolicies/createorupdate#protectionpolicyresource)| OK |
157
+
|200 OK |[Protection PolicyResource](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/createorupdate#protectionpolicyresource)| OK |
158
158
|202 Accepted || Accepted |
159
159
160
160
### Example responses
@@ -279,7 +279,7 @@ If a policy is already being used to protect an item, any update in the policy w
279
279
280
280
[Enable protection for an unprotected Azure VM](backup-azure-arm-userestapi-backupazurevms.md).
281
281
282
-
For more information on the Azure Backup REST APIs, refer to the following documents:
282
+
For more information on the Azure Backup REST APIs, see the following documents:
Copy file name to clipboardExpand all lines: articles/backup/backup-sql-server-azure-troubleshoot.md
+5-8Lines changed: 5 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,6 @@ To configure protection for a SQL Server database on a virtual machine, you must
28
28
|---|---|---|---|
29
29
| Warning | Current settings for this database don't support certain backup types present in the associated policy. | <li>Only a full database backup operation can be performed on the master database. Neither differential backup nor transaction log backup is possible. </li> <li>Any database in the simple recovery model does not allow for the backup of transaction logs.</li> | Modify the database settings such that all the backup types in the policy are supported. Or, change the current policy to include only the supported backup types. Otherwise, the unsupported backup types will be skipped during scheduled backup or the backup job will fail for ad hoc backup.
30
30
31
-
32
31
### UserErrorSQLPODoesNotSupportBackupType
33
32
34
33
| Error message | Possible causes | Recommended action |
@@ -78,7 +77,7 @@ To configure protection for a SQL Server database on a virtual machine, you must
78
77
|---|---|---|
79
78
| Restore failed as the database could not be brought offline. | While you're doing a restore, the target database needs to be brought offline. Azure Backup can't bring this data offline. | Use the additional details on the Azure portal error menu to narrow down the root causes. For more information, see the [SQL Server documentation](https://docs.microsoft.com/sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms). |
| Error message | Possible causes | Recommended action |
84
83
|---|---|---|
@@ -90,7 +89,6 @@ To configure protection for a SQL Server database on a virtual machine, you must
90
89
|---|---|---|
91
90
| The log backup used for recovery contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time as per the SQL guidelines. | When a database is in bulk-logged recovery mode, the data between a bulk-logged transaction and the next log transaction can't be recovered. | Choose a different point in time for recovery. [Learn more](https://docs.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms186229(v=sql.105)).
92
91
93
-
94
92
### FabricSvcBackupPreferenceCheckFailedUserError
95
93
96
94
| Error message | Possible causes | Recommended action |
@@ -125,8 +123,7 @@ Operation is blocked as you have reached the limit on number of operations permi
125
123
126
124
| Error message | Possible causes | Recommended action |
127
125
|---|---|---|
128
-
Operation is blocked as the vault has reached its maximum limit for such operations permitted in a span of 24 hours. | When you have reached the maximum permissible limit for an operation in a span of 24 hours, this error comes. This error usually comes in case of at-scale operations such as modify policy or auto-protection. Unlike in the case of CloudDosAbsoluteLimitReached, there is not much you can do to resolve this state, in fact, Azure Backup service will retry the operations internally for all the items in question.<br> For example: If you have a large number of datasources protected with a policy and you try to modify that policy, it will trigger configure protection jobs for each of the protected items and sometimes may hit the maximum limit permissible for such operations per day.| Azure Backup service will automatically retry this operation after 24 hours.
129
-
126
+
Operation is blocked as the vault has reached its maximum limit for such operations permitted in a span of 24 hours. | When you have reached the maximum permissible limit for an operation in a span of 24 hours, this error comes. This error usually comes when there are at-scale operations such as modify policy or auto-protection. Unlike in the case of CloudDosAbsoluteLimitReached, there is not much you can do to resolve this state, in fact, Azure Backup service will retry the operations internally for all the items in question.<br> For example: If you have a large number of datasources protected with a policy and you try to modify that policy, it will trigger configure protection jobs for each of the protected items and sometimes may hit the maximum limit permissible for such operations per day.| Azure Backup service will automatically retry this operation after 24 hours.
130
127
131
128
## Re-registration failures
132
129
@@ -145,14 +142,14 @@ Check for one or more of the following symptoms before you trigger the re-regist
145
142
146
143
These symptoms may arise for one or more of the following reasons:
147
144
148
-
* An extension was deleted or uninstalled from the portal.
145
+
* An extension was deleted or uninstalled from the portal.
149
146
* An extension was uninstalled from **Control Panel** on the VM under **Uninstall or Change a Program**.
150
147
* The VM was restored back in time through in-place disk restore.
151
148
* The VM was shut down for an extended period, so the extension configuration on it expired.
152
149
* The VM was deleted, and another VM was created with the same name and in the same resource group as the deleted VM.
153
150
* One of the availability group nodes didn't receive the complete backup configuration. This can happen when the availability group is registered to the vault or when a new node is added.
154
151
155
-
In the preceding scenarios, we recommend that you trigger a re-register operation on the VM. For now, this option is available only through PowerShell.
152
+
In the preceding scenarios, we recommend that you trigger a re-register operation on the VM. See [here](https://docs.microsoft.com/azure/backup/backup-azure-sql-automation#enable-backup) for instructions on how to perform this task in PowerShell.
156
153
157
154
## Size limit for files
158
155
@@ -183,6 +180,7 @@ If the string size of the content exceeds 20,000 bytes, the database files are s
183
180
You can override the target restore file path during the restore operation by placing a JSON file that contains the mapping of the database file to the target restore path. Create a `database_name.json` file and place it in the location *C:\Program Files\Azure Workload Backup\bin\plugins\SQL*.
184
181
185
182
The content of the file should be in this format:
183
+
186
184
```json
187
185
[
188
186
{
@@ -223,7 +221,6 @@ SELECT mf.name AS LogicalName FROM sys.master_files mf
223
221
WHERE db.name = N'<Database Name>'"
224
222
```
225
223
226
-
227
224
This file should be placed before you trigger the restore operation.
0 commit comments