Revision Summary Date Revision History Revision Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 1.0 None No changes to the meaning, language, or formatting of the technical content.
details, see section . AppPublisherName Optional Application publisher name. For more details, see section . The response message for this operation can result in the following status codes. Status code Description 200 Operation successfully completed. 400 One or more parameters are not valid. 401 Access to the requested resource is denied. 404 The path does not exist. 409 File item with the new path has existed. Request Body None. Response Body None. Processing Details This operation copies the file item to another location. Timer Events None. Other Local Events None.
200 Operation successfully completed. 400 Invalid parameter. 401 The user is not authorized for web access. 403 Operation is forbidden. 404 Cannot find the user or online user. 500 Internal server Request Body The request body is encoded in XML format. Response Body None. Processing Details None. mailbox/enable?username={username} Enable the mailbox that is assigned to the local user. username: Local user name. HTTP method Description POST Enable the mailbox that is assigned to the local user. POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI: The request message for this operation contains the following HTTP headers. Request header Value
401 Access to the requested resource is denied. This API only supports Administrator calls. 404 The specific resource does not exist. Request Body The request body is encoded in XML format or JSON format based on the value of the Accept header (section ), or in XML format if the Accept header is not present. Response Body None. Processing Details This call will add the specified by the GUIDs in the request body to the group specified by GroupGuid. usergroup/{groupguid}/removeusers Removes users from the specified user group. groupguid: The GUID of the group. See section . HTTP method Description POST Removes users from the specified user group. POST Removes users from the specified user group. This operation is transported by an HTTP POST. The operation can be invoked through the following URI: https://<ServerName>/services/builtin/UserManagement.svc/usergroup/{groupguid}/removeusers The request message for this operation contains the following HTTP headers. Request header Usage Value Canary Optional The user token. Client MUST either pass this header to
details, refer to section . AppVersion Optional The client application version. For more details, refer to section . AppPublisherName Optional The client application publisher name. For more details, refer to section . The response message for this operation can result in the following status codes. Status code Description 200 Operation successfully completed. 400 One or more parameters are not valid. 401 Access to the requested resource is denied. 404 The device specified by the device ID is not registered. Request Body None. Response Body None. Processing Details This call unsubscribes a device from Windows Phone tile updates. Timer Events None. Other Local Events None.
157 157 158 171 171 157 Iusermanagement server 171 172 171 172 187 187 171 Iwindowsphonemanagement server 189 189 189 189 192 192 189 M Messages 20 N 20 18 O 18 P 199 19 19 214 Protocol examples 196 194 193 193 197 195 197 R References 18 18 19 S Security 199 199 Sessionservice server 73 73 73 73 76 76 73 19 T 215 20 20 20 V 19 19